Network type content reproduction system

ABSTRACT

The network type audio system includes a content server storing a large number of music data pieces, an audio client reproducing music, and a controller monitoring and controlling the audio client through the content server. The audio client requests the server to provide the music data of a music piece selected in response to the user&#39;s operation. The content server returns the music data of the selected music piece in response to the request from the audio client. The music data is distributed from the content server to the audio client on the basis of a specified amount. The audio client notifies the content server of its status. The content server notifies the controller of the status of the audio client. The controller displays the status. The controller also instructs the audio client to reproduce the music piece selected in response to the user&#39;s operation through the content server.

TECHNICAL FIELD

The present invention relates to network type content reproducingsystems, and more specifically, to a network type content reproducingsystem having a server, a client connected to the server, and acontroller connected to the server.

BACKGROUND ART

A typical conventional audio system reads out music data from a mediumand reproduces music based on the music data. Such an audio system mustbasically be provided on a room basis, and the overall cost is high.Meanwhile, there has been a concentrated audio system that can store allmusic data in one location and reproduce a selected music piece in eachroom.

In this concentrated audio system, however, a number of interconnectionssuch as those for music signals and control signals must be provided ineach room. One music piece can be reproduced at a time in all the roomsbut a music piece cannot be reproduced from the beginning in a roomwhile the same music piece is in the process of being reproduced inanother room.

When an application program for music reproduction is installed in ageneral-purpose PC, music data can be obtained from a site on theInternet and music can be reproduced based on the data, but the datamust be completely received before the music is reproduced midway orfast-forwarded or reversed just like a music CD. More specifically, thespecial reproducing manners cannot be achieved for data yet to bereceived.

DISCLOSURE OF THE INVENTION

It is an object of the invention to provide a network type contentreproducing system that permits a client to freely select and reproducean audio or video content stored in a server.

Another object of the invention is to provide a network type contentreproducing system that permits the user to freely reproduce data notyet received by a client like reproducing the data from midway.

Yet another object of the invention is to provide a network type contentreproducing system that permits a client to continuously reproducecontents in a client-server environment.

A still further object of the invention is to provide a network typecontent reproducing system that eliminates competition betweencontinuous reproducing instructions to a client.

An additional object of the invention is to provide a client with anautomatic connection recovery function that can quickly recoverconnection when the client is disconnected from a server.

A network type content reproducing system according to the inventionincludes a server and at least a first client connected to the server.The server includes storing means for storing a plurality of contents(such as music contents and visual contents). The first client includescontent request means for requesting the server to provide a contentselected among the plurality of contents. The server further includescontent returning means for returning the content selected in responseto the request from the first client to the first client. The firstclient further includes reproducing means for reproducing the returnedcontent.

In the network type content reproducing system, a desired content isselected among the plurality of contents stored in the server inresponse to a request from the client. The selected content istransmitted from the server to the client and reproduced. Therefore, theclient can freely select among the plurality of contents stored in theserver and reproduce a selected content.

When the content is a music content, a desired music piece is selectedamong the large number of pieces stored in the server in response to arequest from the first client. The data of the selected piece istransmitted to the first client, and the selected music piece isreproduced based on the data. Therefore, the first client can freelyselect among the plurality of music pieces stored in the server andreproduce a selected piece.

The first client is preferably attached in an outlet box provided in awall.

In this way, the user can listen to music or watch video without thefirst client provided inside the room.

Preferably, the first client includes content list request means forrequesting the sever to provide a content list of a plurality ofcontents. The server further includes content list returning means forreturning the content list in response to the request from the firstclient. The first client further includes content list receiving meansfor receiving the content list returned from the server. The contentrequest means selects a content to be requested in the content list.

In this way, the first client can obtain a content list from the serverand reproduce a desired content selected in the list.

More preferably, the content list request means requests the server toprovide a specified amount of a content list, preferably a part of thecontent list. The content list returning means responds to the requestfrom the first client to return the specified amount of the contentlist, preferably a part of the content list.

In this way, only a part of the content list is transmitted to the firstclient from the server, and therefore the memory capacity necessary forstoring the content list in the first client may be small.

More preferably, the content list request means transmits a list requestcommand including an obtaining start index indicating the first contentto be obtained from the server by the first client and an obtainingnumber indicating the number of contents to be obtained from the serverby the first client. The content list returning means returns thecontent list including contents as many as the obtaining number from thefirst content indicated by the obtaining start index in response to thelist request command.

More preferably, the content list returning means further returns thenumber of contents included in the content list to be returned and thenumber of the remaining contents left out of the content list to bereturned.

In this way, the first client can be informed of the number of thecontents remaining in the content list that are not yet obtained and cantherefore request the server to provide the rest of the content list.

Preferably, the first client further includes category list requestmeans for requesting the server to provide a category list of aplurality of categories. The server further includes means responsive tothe request from the first client for returning the category list. Thefirst client further includes means for receiving the category listreturned from the server. The content list request means selects acategory of the contents in the content list to be requested in thereceived category list.

In this way, the first client can obtain a category list from the serverto begin with and then select a desired category in the list. The firstclient then obtains a content list and selects a desired content in thelist. Therefore, in selecting, the large number of contents cangradually be narrowed down to a desired content.

Preferably, the content list request means transmits a list constructionkey necessary for producing the content list to the server. The contentlist returning means produces a content list based on the listconstruction key.

In this way, the first client can obtain a content list by sending thelist construction key to the server when the client needs the contentlist, so that the client does not have to store the obtained contentlist.

Preferably, the content request means requests the server to provide apredetermined amount of a content. The content returning means returnsthe predetermined amount of the content in response to the request fromthe first client. The content request means repeats the request for thecontent until the content is obtained in its entirety.

In this way, only a part of the content is transmitted from the serverto the first client, and therefore the memory capacity necessary forstoring the content in the first client may be small.

The content request means further preferably calculates an obtainingstart address indicating the first address of the predetermined amountof the content and transmits the address to the server. The contentreturning means returns the predetermined amount of the content from theobtaining start address transmitted from the first client.

More preferably, the content request means transmits a content transferrequest command including the obtaining start address and an obtainingdata length indicating the length of the content to be obtained from theserver by the first client. The content returning means returns thecontent for the obtaining data length from the obtaining start addressin response to the content transfer request command.

In this way, the obtaining start address is arbitrarily set, so that theclient can carry out special reproducing to a content not yet received.

More preferably, the content request means adds the obtaining datalength to the previous obtaining start address to calculate the nextobtaining start address.

More preferably, the first client further includes means responsive tothe user's operation for setting first and second addresses and meansfor setting the obtaining start address to the first address when thecalculated obtaining start address exceeds the second address.

In this way, the first client can repeat obtaining the content from thefirst address to the second address and reproduce the obtained content.

Alternatively, the first client further includes means responsive to theuser's operation for setting a desired address and means for setting theobtaining start address to the desired address.

In this way, the first client can obtain the content from the desiredaddress and reproduce the content from midway.

Preferably, the first client further includes means responsive to theuser's operation for setting a prescribed skip amount and means forshifting the obtaining start address by the set skip amount.

In this way, the first client can obtain the content discontinuously andcan carry out fast forward reproducing or fast reverse reproducing.

Preferably, the first client further includes means for transmitting theidentification information of the selected content to the server. Theserver includes means responsive to the identification informationtransmitted from the first client for returning the offset of theselected content to the first client. The first client further includesmeans for detecting the start of the selected content based on theoffset returned from the server.

In this way, the first client detects the start of the content based onthe offset of the content transmitted from the server and therefore canimmediately reproduce the content.

Preferably, the first client further includes means for transmitting theidentification information of the selected content to the server. Theserver further includes means responsive to the identificationinformation transmitted from the first client for returning the size ofthe selected content to the first client. The first client furtherincludes means for detecting the end of the selected content based onthe size returned from the server.

In this way, the first client detects the end of the content based onthe size of the content transmitted from the server and can thereforeimmediately end reproducing.

Preferably, the content request means requests the server to provide aspecified amount of a content. The content returning means returns thespecified amount of the content in response to the request from thefirst client. The content request means changes the specified amount ofthe content to be requested to the server.

In this way, the first client can reduce the specified amount of thecontent when the load on the server is large and increase the specifiedamount of the content when the load on the server is small, so that thecontent amount can appropriately be adjusted depending on the load onthe server.

In addition, the server returns only a “part of music piece data”specified by the client, and therefore the client can carry out specialreproducing (such as fast forward, fast reverse, and midway reproducing)to data not yet received by arbitrarily changing the “part of the musicdata” to be specified. The server transmits only the “part of musicpiece data” and therefore if the client cannot successfully receive thedata, only the part the client cannot receive may be received again fromthe server, and the receiving failure can quickly be coped with.

When the format of a music piece requested by the client is a compresseddata format (such as MP3), the amount of data to be specified may bereduced in order to alleviate the load on the server. This is becausethe compressed data has its data amount increased once it is decoded atthe time of reproducing.

Preferably, the first client further includes means for transmittingclient information related to the first client to the server every timethe client information changes.

In this way, the client information is not constantly transmitted to theserver from the first client, but transmitted only when there is achange. Therefore, the server can manage the up-to-date clientinformation of the first client without increasing the network traffic.

Preferably, the network type content reproducing system further includesa second client connected to the server through a network for monitoringthe first client.

In this way, the user can be informed of the operation state of thefirst client through the second client different from the first client.

More preferably, the first client further includes means fortransmitting client information related to the first client to theserver. The server includes means for receiving the client informationtransmitted from the first client and means for transmitting thereceived client information to the second client. The second clientincludes means for receiving the client information transmitted from theserver.

In this way, the user can be informed of the information related to thefirst client such as the connection state with the server, the clienttype, the present operation state, and the present sound volume throughthe second client different from the first client.

Preferably, the server transmits the client information to the secondclient through a push port for forcibly transmitting a request to thesecond client.

In this way, the server can transmit the client information to thesecond client if there is no request from the second client.

Preferably, the second client further includes means for displaying thereceived client information and means for changing the display of thereceived client information when the client information is changed.

Preferably, the second client further includes content list requestmeans for requesting the server to provide a content list of a pluralityof contents. The server further includes content list returning meansresponsive to the request from the second client for returning thecontent list. The second client further includes content list receivingmeans for receiving the content list returned from the server.

Preferably, the client information includes a list construction keynecessary for producing a content list. The content list request meanstransmits the list construction key to the server when the listconstruction key included in the received client information is changed.The content list returning means produces the content list based on thelist construction key transmitted from the second client.

Preferably, the second client receives the client informationtransmitted from the server when the second client is connected to theserver.

In this way, the second client is connected to the server once the powersupply is turned on and can obtain the client information related to thefirst client from the server.

More preferably, the client information includes a list construction keynecessary for producing a content list. The content list request meanstransmits the list construction key included in the received clientinformation to the server. The content list returning means produces thecontent list based on the list construction key transmitted from thesecond client.

In this way, if the power supply is turned off after the second clientinstructs the first client to reproduce a content, and the content listbeing reproduced is lost, the second client can obtain the listconstruction key when the power supply is turned on again. Therefore,the second client needs only transmit the obtained list construction keyto the server, so that the lost content list can be regained from theserver.

Preferably, the client information includes the name of a data format ofa content reproducible by the first client. The second client includesmeans for displaying the name of the data format name of thereproducible content based on the received client information.

In this way, the user can be informed of the data format reproducible bythe first client through the second client different from the firstclient.

More preferably, the second client further includes means for obtaininga content list of a plurality of contents from the server and means fordisplaying a content reproducible by the first client among the contentsincluded in the obtained content list and displaying a content thatcannot be reproduced by the first client in a different manner from thereproducible content or not displaying the irreproducible contents.

In this way, contents that cannot be reproduced by the first client arenot displayed, so that the user can be prevented from selecting any ofthe irreproducible contents.

Preferably, the second client includes means for determining whether aclient to be monitored is the first client.

In this way, if the client to be monitored by the second client is notthe first client, the second client does not monitor, and thereforeerroneous operation can be prevented.

Preferably, the second client includes means for obtaining a monitoringhandle necessary for monitoring the first client and means formonitoring the first client using the obtained monitoring handle.

In this way, a second client without the monitoring handle does notmonitor the first client and therefore the network traffic can bereduced.

Preferably, the network type content reproducing system further includesa second client connected to the server through a network forcontrolling the first client.

More preferably, the second client includes server request means forrequesting the server to control the first client. The server furtherincludes means responsive to the request from the second client forcontrolling the first client.

In this way, the user can control the first client through the serverfrom the second client different from the first client.

Preferably, the server request means transmits information forspecifying the first client and information for specifying the selectedcontent to the server.

In this way, the user can have a desired content reproduced by the firstclient.

Preferably, the second client includes means for determining whether aclient to be controlled is the first client.

In this way, the second client does not control a client if the clientis not the first client, and therefore erroneous operation can beprevented.

Preferably, the second client includes means for determining whether thedata format of the selected content matches the data format of any ofcontents that can be reproduced by the first client and means forinstructing the first client to reproduce the content based on the dataof the selected content when the data formats match.

In this way, the second client instructs the first client to reproduce acontent only if the content is reproducible by the first client andtherefore erroneous operation can be prevented.

Preferably, the second client includes means for obtaining a controlhandle necessary for controlling the first client and means forcontrolling the first client using the obtained control handle.

In this way, the second client without the control handle will notcontrol the first client, and therefore the network traffic can bereduced.

Preferably, the first client further includes means for transmitting acompletion status to the server when the first client finishesreproducing a content as instructed by the second client andtransmitting a stop status different from the completion status itselfwhen the first client finishes reproducing a content selected by thefirst client or stops reproducing the content midway in response to theuser's operation.

In this way, the server can distinguish the completion status from thestop status, and therefore the server can determine whether the firstclient has finished reproducing a content instructed by the secondclient or a content selected by the first client or stopped reproducinga content midway in response to the user's operation.

Preferably, the server includes means for receiving the completionstatus transmitted from the first client and transmitting the completionstatus to the second client. The second client includes means responsiveto the completion status transmitted from the server for instructing thefirst client to reproduce the content next to the content that has beenreproduced to the end.

In this way, the first client that has finished reproducing the contenttransmits a completion status to the second client that has instructedreproducing of the content, and therefore the second client can causethe first client to continuously reproduce contents based on the contentlist.

Preferably, a network type content reproducing system further includes aplurality of second clients connected to the server through a network tocontrol the first client. The second clients each include reproducinginstruction means for instructing the first client to reproduce acontent. The content reproducing means of the first client reproduces acontent in response to an instruction from the second client. The firstclient further includes means for transmitting a completion status tothe server when the content has been reproduced to the end. The serverfurther includes means for receiving a completion status transmittedfrom the first client and transmitting the completion status to thesecond client that has instructed the first client among the pluralityof second clients, while transmitting a stop status to the other secondclients. The reproducing instruction means of the second client respondsto the completion status transmitted from the server to instruct thefirst client to reproduce the content the next to the content that hasbeen reproduced to the end.

In this way, the first client that has finished reproducing the contenttransmits a completion status to the second client that has instructedthe reproducing of the content through the server, so that the secondclient correctly instructs the first client to carry out continuousreproducing. Meanwhile, the server transmits a stop status to the othersecond clients, and therefore the second client is aware that the firstclient is in an operation stopped state and will not incorrectlyinstruct the first client to carry out continuous reproducing.

Preferably, the first client further includes broadcast means forbroadcasting prescribed information. The server includes meansresponsive to the prescribed information broadcast from the first clientfor returning server specifying information to specify the server to thefirst client. The first client includes means for receiving the serverspecifying information returned from the server and registering theinformation in a server list.

In the network type content reproducing system, when the clientbroadcasts prescribed information to a network and there is a serverconnected to the network, the server transmits its server specifyinginformation (such as the IP address and the port number) to the client.Therefore, the client can search and find the server existing on thenetwork.

Preferably, the first client further includes means for determiningwhether the server specifying information is registered in the serverlist. When the server specifying information is not registered in theserver list based on the result of the determination, the broadcastmeans broadcasts the prescribed information again.

In this case, the first client starts searching for a server if noserver specifying information is registered in the server list andcontinues to search until at least one server is found.

Preferably, the first client further includes means for accessing aserver on the Internet when the number of broadcasting operation by thebroadcast means reaches a prescribed number of times or time forbroadcasting by the broadcast means reaches a prescribed time period.

In this way, the first client does not continue to search for a serverif there is no server existing on the local network and finds a serveron the Internet instead.

Preferably, the first client further includes means for establishingconnection at a command port for transmitting/receiving a commandbetween the server and the first client and means for establishingconnection at a push port for forcing a request to be transmitted to thefirst client from the server.

In the network type content reproducing system, commands or statuses aretransmitted/received between the server and a client through the commandport. A command from the server is forced to be transmitted to a clientthrough the push port.

Preferably, the first client further includes means for transmitting aclient index request command to the server through the command port. Theclient index request command is necessary for identifying the firstclient. The server further includes means responsive to the client indexrequest command transmitted by the first client for returning the clientindex to the client. The first client further includes means fortransmitting the client index returned from the server to the serverthrough the push port.

Preferably, there are a plurality of the first clients. The serverincludes connection limiting means for limiting the number ofconnectable clients.

Preferably, the connection limiting means disconnects from the firstclient that has been already connected based on a prescribed priorityorder when another first client that has not yet been connected tries tobe connected to the connection limiting means.

Preferably, another network type content reproducing system according tothe invention includes a server, a first client connected to the serverthrough a network, AV equipment connected to the first client, and asecond client connected to the server through the network to control theAV equipment. The second client includes means for transmitting acontrol command for controlling the AV equipment to the server. Theserver includes means for transmitting the control command transmittedfrom the second client to the first client. The first client includesmeans for transmitting the control command transmitted from the serverto the AV equipment. The AV equipment is controlled in response to thecontrol command transmitted from the first client.

In this way, the control command is transmitted to the first client fromthe second client through the server. The AV equipment is controlled inresponse to the control command. Therefore, the second client cancontrol the AV equipment.

Another network type content reproducing system according to theinvention includes a server, a first client connected to the server, AVequipment connected to the first client, and a second client connectedto the server through a network to monitor the AV equipment. The AVequipment includes means for transmitting information related to the AVequipment to the first client. The first client includes AV equipmentinformation transmitting means for transmitting the informationtransmitted from the AV equipment to the server. The server includesmeans for transmitting the information transmitted from the first clientto the second client.

In this way, the information related to the AV equipment is transmittedto the second client through the first client and the server. Therefore,the second client can monitor the AV equipment based on the information.

Preferably, the AV equipment information transmitting means of the firstclient transmits the frequently changing information at prescribedintervals.

In this way, the network traffic can be reduced.

Preferably, the server further includes firmware update means forupdating firmware in the first client.

In this way, the firmware in the first client is automatically updatedby the server.

Preferably, the server further includes means for registeringinformation related to a plurality of firmware pieces suitable for thefirst client and firmware list transmitting means for transmitting afirmware list of the registered information related to the plurality offirmware pieces to the first client. The first client further includesmeans for receiving the firmware list transmitted from the server andfirmware request means for requesting the server to transmit firmwareselected in the received firmware list. The firmware update meansreturns the selected firmware to the first client in response to therequest from the first client.

In this way, the firmware in the first client is not always updated tothe up-to-date version, but updated to an appropriately selectedversion.

Preferably, the first client further includes means for transmittingclient information related to the first client to the server. The serverfurther includes means for producing a firmware list based on the clientinformation transmitted from the first client.

In this way, a firmware list including firmware informationcorresponding to the first client can be produced.

Preferably, the first client requests the server to provide a specifiedamount of firmware, particularly a part of the firmware. The firmwareupdate means returns the specified amount of the firmware, preferably apart of the firmware in response to the request from the first client.

In this way, the server transmits only the specified amount of thefirmware, and therefore if the client cannot successfully receive thefirmware, only the part the client cannot receive may be received againfrom the server, and the receiving failure can quickly be coped with.Since only a part of the firmware list is transmitted from the server tothe first client, the memory capacity necessary for storing the firmwarelist in the first client may be small.

Another network type content reproducing system according to theinvention includes a server, a first client connected to the server, anda plurality of second clients connected to the server. The serverincludes content storing means for storing a plurality of contents. Thesecond clients each include means for specifying a content among theplurality of contents and instructing the first client to reproduce thespecified content. The first client includes means responsive to theinstruction from the second client for reproducing the specified contentand means for transmitting a completion status to the server when thecontent has been reproduced to the end. The server further includesstatus transmitting means for selecting one of the plurality of secondclients and transmitting the completion status to the selected secondclient in response to the completion status received from the firstclient. The second clients each further include means for specifying acontent next to the content that has been reproduced to the end by thefirst client and instructing the first client to reproduce the specifiedcontent in response to the completion status received from the server.

Preferably, the server further includes means for managing thepriorities of the second clients that can control the first client. Thestatus transmitting means selects a second client with the highestpriority as the second client to receive the transmitted completionstatus. Alternatively, the server further includes means for storing theidentification information of the second client that has instructedreproduction. The status transmitting means selects the second clientthat has instructed reproduction as the second client to receive thecompletion status based on the stored identification information of thesecond client.

In this system, when the server receives a completion status from thefirst client that has finished reproducing a content, the server selectsa second client and transmits the completion status to the secondclient. Therefore, only one second client instructs the first client tocarry out continuous reproducing. As a result, the system eliminatescompetition between continuous reproducing instructions to a firstclient, and the first client can continuously reproduce contents.

Preferably, the status transmitting means transmits a stop status to thesecond client other than the second client with the highest priority.

In this way, the stop status instead of the completion status istransmitted to the second clients other than the second client with thehighest priority, and therefore the other second clients can simplymonitor the state of the first client without taking any positiveaction.

Another network type content reproducing system according to theinvention includes a server, a first client connected to the server, anda plurality of second clients connected to the server. The serverincludes content storing means for storing a plurality of contents. Thesecond clients each include control handle obtaining means for obtaininga control handle necessary for controlling the first client and meansfor specifying a content among the plurality of contents after obtainingthe control handle and instructing the first client to reproduce thespecified content. The first client includes means responsive to theinstruction from the second client for reproducing the specified contentand means for transmitting a completion status to the server when thecontent has been reproduced to the end. The server further includesmeans for transferring the completion status transmitted from the firstclient to each of the second clients. The second clients each furtherinclude means for specifying a content next to the content that has beenreproduced to the end by the first client in response to the completionstatus received from the first client whose control handle is obtainedby the second client and instructing the first client to reproduce thespecified content.

In this system, the second client obtains a control handle necessary forcontrolling the client and then instructs the first client to reproducethe content. The first client transmits a completion status once acontent has been reproduced to the end. In response to a completionstatus received from the first client whose control handle is obtainedby the second client, the second client instructs the first client tocarry out continuous reproducing. Consequently, the system eliminatescompetition between continuous reproducing instructions to the firstclient and the first client can continuously reproduce contents.

Preferably, the control handle obtaining means, upon obtaining a controlhandle, prohibits the other second clients from obtaining the controlhandle.

In this way, a plurality of second clients cannot obtain the controlhandle for the first client at a time, and therefore competition betweenreproducing instructions to the first client can completely beeliminated.

More preferably, the first client further includes means fortransmitting a stop status to the server when the first client stopsreproducing the content midway. The server further includes means fortransferring the stop status transmitted from the first client to eachof the second clients. The second clients each further include means forcanceling the prohibition of obtaining the control handle in response tothe stop status received from the first client whose control handle isobtained by the second client.

In this way, the first client that has stopped reproducing the contentmidway transmits a stop status to all the second clients and a secondclient that receives the stop status from the first client whose controlhandle is obtained by the second client releases the control handle.Therefore, any of the second clients can obtain the control handle forthe first client.

Another network type content reproducing system according to theinvention includes a server, a first client connected to the server, anda second client connected to the server. The server includes contentstoring means for storing a plurality of contents. The second clientincludes means for specifying a content among the plurality of contentsand instructing the first client to reproduce the specified content. Thefirst client includes means responsive to the instruction from thesecond client for reproducing the specified content, and means fortransmitting a completion status to the server when the content has beenreproduced to the end. The server further includes continuousreproducing instruction means responsive to the completion statusreceived from the first client for specifying a content next to thecontent that has been reproduced to the end by the first client andinstructing the first client to reproduce the specified content.

In this system, the first client that has reproduced a content to theend transmits a completion status to the server, and then the serveritself instructs the first client to carry out continuous reproducing.Consequently, the system eliminates competition between continuousreproducing instructions to the first client, and the first client cancontinuously reproduce contents.

Preferably, the server further includes means for storing a listconstruction key necessary for producing a content list of contents tobe reproduced by the first client and means for producing the contentlist based on the list construction key. The continuous reproducinginstruction means instructs the first client to reproduce the contentaccording to the content list.

In this way, the server stores the list construction key and producesthe content list based on the list construction key, so that the contentto be reproduced next can be specified.

Another network type content reproducing system includes a server, afirst client connected to the server, and a second client connected tothe server. The server includes content storing means for storing aplurality of contents. The second client includes means for specifying acontent among the plurality of contents and instructing the first clientto reproduce the specified content and means for transmitting a listconstruction key necessary for producing a content list of contents tobe reproduced by the first client to the first client. The first clientincludes means responsive to the instruction from the second client forreproducing the specified content and means for transmitting the listconstruction key transmitted from the second client to the server. Theserver further includes means for producing the list of contents basedon the list construction key transmitted from the first client andtransmitting the produced content list to the first client. The firstclient further includes means for reproducing a content next to thecontent that has been reproduced to the end by the first clientaccording to the content list transmitted from the server.

In this system, the server transmits the content list produced based onthe list construction key to the first client. The first client carriesout continuous reproducing on its own according to the content list.Consequently, the system eliminates competition between continuousreproducing instructions to the first client, and the first client cancontinuously reproduce contents.

A client in a network type content reproducing system according to theinvention includes content request means for requesting the server toprovide a digital content selected among a plurality of digital contentsstored in the server and reproducing means for reproducing the digitalcontent returned from the server in response to the request. There are aplurality of servers. The client further includes connection means anddetermination means. The connection means connects with any one of theplurality of servers. The determination means determines whether theconnection with the server by the connection means is maintained atprescribed intervals. The connection means reconnects with the serverwhen the determination means determines that the connection with theserver is closed.

The client checks the connection state with the server at prescribedintervals. When the connection with the server is closed, the clientcarries out re-connection with the server. Therefore, if the client isdisconnected from the server because of abnormality, the client canquickly recover the connection on its own.

Preferably, the connection means connects with another server when theconnection with the server cannot be reestablished.

In this way, if the connection cannot be reestablished with the sameserver connected before the disconnection, the client quickly connectswith another server. Consequently, the client is not left in thedisconnected state from the server.

Preferably, the connection means transmits the client status to thereconnected server before the connection is closed.

In this way, the client transmits the client status before thedisconnection to the reconnected server, and therefore the client canrecover the connection state with the server as before. Consequently,the user can use the client without being aware of the re-connection ofthe client.

BRIEF DESCRIPTION OF THE DRAWINGS

FIG. 1 is a functional block diagram of the general configuration of anetwork type audio system according to an embodiment of the invention;

FIG. 2 is a functional block diagram of the configuration of each serverin FIG. 1;

FIG. 3 is a functional block diagram of the configuration of each audioclient in FIG. 1;

FIG. 4 is a functional block diagram of the configuration of eachcontroller in FIG. 1;

FIG. 5 is a flowchart for use in illustration of the operation of theserver and the audio client in FIGS. 1 to 3 in an initial connectionphase;

FIG. 6 is a flowchart for use in illustration of server search operationby the audio client in FIG. 5;

FIG. 7 is a flowchart for use in illustration of connection operation bythe client and the server in FIG. 5;

FIG. 8 is a diagram showing push operation by the server after theconnection operation in FIG. 7;

FIG. 9 is the continuation of FIG. 8 showing server request operation tothe audio client from the controller to the server;

FIG. 10 is a diagram showing the operation of notifying the controllerof a status from the audio client through the server as continued fromFIG. 9;

FIG. 11 is a flowchart for use in illustration of client informationtransmitting operation by the audio client in FIG. 5;

FIG. 12 is a flowchart for use in illustration of initialization andmain operation by the server in FIGS. 1 and 2;

FIG. 13 shows a client information database stored in the server in FIG.2;

FIG. 14 shows a content information database stored in the server inFIG. 2;

FIG. 15 shows a firmware information database stored in the server inFIG. 2;

FIG. 16 is a flowchart for use in illustration of a subroutine torespond to server search in FIG. 12;

FIG. 17 is a flowchart for use in illustration of a subroutine incommand port connection accepting processing in FIG. 12;

FIG. 18 is a flowchart for use in illustration of a subroutine in pushport connection accepting processing (case 1) in FIG. 12;

FIG. 19 is a flowchart for use in illustration of a subroutine in thepush port connection accepting processing (case 2) in FIG. 12;

FIG. 20 is a flowchart for use in illustration of a subroutine incommand processing in FIG. 15;

FIG. 21 is a flowchart for use in illustration of a subroutine in statusnotification command processing in FIG. 20;

FIG. 22 is a flowchart for use in illustration of a subroutine in serverrequest issue command processing in FIG. 20;

FIG. 23 is a flowchart for use in illustration of the operation ofobtaining a music list and reproducing by the server and the audioclient in FIGS. 1 to 3;

FIG. 24 is a flowchart for use in illustration of the operation ofobtaining a music list by the audio client in FIG. 23;

FIG. 25 is a flowchart for use in illustration of the operation ofobtaining a genre list and a music list in FIG. 24;

FIG. 26 shows a region that stores the genre list obtained in FIG. 25;

FIG. 27 is a diagram of the record structure of the content informationdatabase in FIG. 14;

FIG. 28 is a flowchart for use in illustration of the operation ofproducing a genre list by the server in FIG. 25;

FIG. 29 shows a region that stores the music list obtained in FIG. 25;

FIG. 30 is a flowchart for use in illustration of the operation ofproducing a music list by the server in FIG. 25;

FIG. 31 shows the format of a list request command in FIG. 25;

FIG. 32 shows the format of search data in FIG. 25;

FIGS. 33A to 33C show the transition state of a buffer memory in theoperation of obtaining a music list in FIG. 25;

FIG. 34 is a flowchart for use in illustration of the operation ofobtaining a genre list and a music list as well as the operation ofobtaining an album list in FIG. 25;

FIG. 35 is a flowchart for use in illustration of the operation ofspecifying a music piece, reproducing, and stopping by an audio clientas well as the operation of preparing for music piece distribution anddistributing by a server in FIG. 23;

FIG. 36 is a flowchart continued from FIG. 35;

FIG. 37 shows a music piece information request command in FIG. 35;

FIG. 38 shows music piece information in FIG. 35;

FIG. 39 shows a music piece reproducing preparation command in FIG. 35;

FIG. 40 shows an error code in FIG. 35;

FIG. 41 shows a music piece data transfer request command in FIG. 35;

FIG. 42 shows music piece data in FIG. 35;

FIG. 43 shows the structure of a buffer memory for storing the musicpiece data in FIG. 42;

FIG. 44 shows the state of how music piece data for one buffer is storedfrom the start of the music piece in the buffer memory in FIG. 43;

FIG. 45 shows the state of how music data for all the buffers are storedas continued from FIG. 44;

FIG. 46 shows the state of how the first buffer outputs music piece dataas continued from FIG. 45;

FIG. 47 shows the state of how a space for one buffer is generated ascontinued from FIG. 46;

FIG. 48 shows the state of how the space in the buffer is filled ascontinued from FIG. 47;

FIG. 49 is a flowchart for use in illustration of fast forwardreproducing by the client and server in FIGS. 1 to 3;

FIG. 50 is a flowchart for use in illustration of pause operation by theclient and server in FIGS. 1 to 3;

FIG. 51 is a flowchart for use in illustration of connection operationby the controller and server in FIG. 1;

FIG. 52 is a flowchart for use in illustration of the operation ofobtaining a monitoring handle and a control handle in FIG. 51;

FIG. 53 shows status notification to a plurality of controllers from aplurality of audio clients by the server;

FIG. 54 shows status notification when a controller obtains a monitoringhandle in FIG. 54;

FIG. 55 is a flowchart for use in illustration of the operation ofmonitoring an audio client by a controller in FIG. 1;

FIG. 56 is a flowchart for use in illustration of details of themonitoring operation in FIG. 55;

FIG. 57 is a flowchart for use in illustration of the operation ofcontrolling the audio client by the controller in FIG. 1;

FIG. 58 is a flowchart for use in illustration of a subroutine incontrol command processing by the audio client in FIG. 57;

FIG. 59 shows a subroutine in reproducing control operation in FIG. 58;

FIG. 60 shows details of a client type included in the clientinformation database in FIG. 13;

FIG. 61 is a flowchart for use in illustration of the operation ofdisplaying a music list in the reproducing control in FIG. 59;

FIG. 62 shows a screen showing the display of a music list related to anaudio client capable of reproducing both MP3 and WAV in the music listdisplay in FIG. 61;

FIG. 63 shows a screen showing the display of a music list related to anaudio client that can reproduce MP3 but cannot reproduce WAV in themusic list display in FIG. 61;

FIG. 64 is a flowchart for use in illustration of the operation ofreproducing instruction processing by the user in the reproducingcontrol in FIG. 59;

FIG. 65 shows how a reproducing command is transmitted in continuousreproducing control by the controller in FIG. 1;

FIG. 66 shows how completion and stop statuses are transmitted ascontinued from FIG. 65;

FIG. 67 is a flowchart for use in illustration of the operation oftransmitting the completion and stop statuses in FIG. 66;

FIG. 68 shows how a reproducing command is transmitted as continued fromFIG. 66;

FIG. 69 shows the structure of a list construction key used in thecontinuous reproducing control in FIGS. 65 to 68;

FIG. 70 shows the kinds of filters included in the list construction keyin FIG. 69;

FIG. 71 is a sequence diagram for use in illustration of continuousreproducing control operation using the list construction key in FIG.69;

FIG. 72 is a flowchart for use in illustration of completion processingoperation by the controller in FIGS. 56 and 71;

FIG. 73 is a flowchart for use in illustration of continuous reproducingprocessing with priorities;

FIG. 74 is a functional block diagram of the continuous reproducingprocessing in FIG. 73;

FIG. 75 is a functional block diagram of the continuous reproducingprocessing when the controller with the highest priority is disconnectedin the continuous reproducing processing in FIG. 73;

FIG. 76 is a flowchart for use in illustration of the operation ofcontinuous reproducing processing using a control handle;

FIG. 77 is a functional block diagram of the continuous reproducingprocessing in FIG. 76;

FIG. 78 is a functional block diagram of the continuous reproducingprocessing by a content server;

FIG. 79 is a flowchart for use in illustration of the operation of thecontinuous reproducing processing in FIG. 78;

FIG. 80 is a functional block diagram of the continuous reproducingprocessing when there are a plurality of audio clients in the continuousreproducing processing in FIG. 78;

FIG. 81 is a functional block diagram of the continuous reproducingprocessing when there are a plurality of content servers in thecontinuous reproducing processing in FIG. 80;

FIG. 82 is a functional block diagram of the continuous reproducingprocessing when the content server is switched in the continuousreproducing processing shown in FIG. 81;

FIG. 83 is a functional block diagram of the continuous reproducingprocessing when there are a plurality of controllers in the continuousreproducing processing in FIG. 81;

FIG. 84 is a flowchart for use in illustration of the operation ofcontinuous reproducing processing by an audio client on its own;

FIG. 85 is a flowchart for use in illustration of the operation ofcontinuous reproducing processing using a reproducing instructionmanagement table;

FIG. 86 is a functional block diagram of details of the continuousreproducing processing in FIG. 85;

FIG. 87 is a flowchart for use in illustration of details of thereproducing instruction management processing in FIG. 85;

FIG. 88 is a functional block diagram of continuous reproducingprocessing when the content server is switched in the continuousreproducing processing in FIG. 85;

FIG. 89 is a flowchart for use in illustration of details of the serverswitching processing in FIG. 85;

FIG. 90 is a functional block diagram of the configuration of a networktype audio system including a server, a controller, an AVR client, andan AV receiver;

FIG. 91 is a functional block diagram of the flow of a status and acommand in the network type audio system in FIG. 90;

FIG. 92 is a flowchart for use in illustration of the control operationof an AV receiver by the controller in the network type audio system inFIGS. 90 and 91;

FIG. 93 is a functional block diagram of the transfer path of a controlcommand and a status in the network type audio system in FIG. 90;

FIG. 94 is a flowchart for use in illustration of the operation oftransmitting a command and a status in FIG. 93;

FIGS. 95A to 95C show a control command in the stages in FIG. 94;

FIGS. 96A to 96C show statuses in the stages in FIG. 94;

FIG. 97 is a flowchart for use in illustration of how the controllerraises the volume of the AV receiver AVR through the AVR client in thenetwork type audio system in FIGS. 90 to 96C;

FIG. 98 is a flowchart for use in illustration of the operation of theAVR client when the status of the AV receiver is transferred to theserver in the network type audio system in FIGS. 90 to 96C;

FIG. 99 is a flowchart for use in illustration of the operation of theAVR client in the network type audio system in FIGS. 90 to 96C when acontrol command from the server is transferred to the AV receiver;

FIG. 100 is a flowchart for use in illustration of an improvement on theoperation in FIG. 99;

FIG. 101 is a flowchart for use in illustration of firmware updatingoperation by the client and server in FIG. 1;

FIG. 102 is a flowchart for use in illustration of details of thefirmware updating operation in FIG. 101;

FIG. 103 is a flowchart for use in illustration of the operation ofproducing a firmware list in FIG. 102;

FIG. 104 is a flowchart for use in illustration of the operation oftransmitting the firmware list in FIG. 102;

FIG. 105 is a front view of the outer structure of an audio clientaccording to another embodiment of the invention;

FIG. 106 is a side view of the audio client in FIG. 105;

FIG. 107 is a functional block diagram of the general structure of anetwork type audio system and the Internet according to anotherembodiment of the invention;

FIG. 108 is a flowchart for use in illustration of server searchoperation in the network type audio system in FIG. 107;

FIG. 109 is a flowchart for use in illustration of the operation oftransferring music piece data according to another embodiment of theinvention;

FIG. 110 is a comparison table that is referred to in steps S16021 andS16061 in FIG. 109;

FIG. 111 is a flowchart for use in illustration of the skip reproducingoperation of an audio client according to another embodiment of theinvention;

FIG. 112 is a table showing a music list stored in the memory of theaudio client in the skip reproducing operation in FIG. 111;

FIG. 113 is a flowchart for use in illustration of repetitivereproducing operation by an audio client according to another embodimentof the invention;

FIG. 114 is a flowchart for use in illustration of midway reproducingoperation by an audio client according to another embodiment of theinvention; and

FIG. 115 is a flowchart for use in illustration of monitoring processingand connection recovery processing by an audio client according toanother embodiment of the invention.

BEST MODE FOR CARRYING OUT THE INVENTION

Now, embodiments of the invention will be described in conjunction withthe accompanying drawings, in which the same or corresponding portionsare denoted by the same reference characters and the same description isequally applied.

TABLE OF CONTENTS

1. Preferred Embodiment

1.1. Configuration

1.1.1. General Configuration

1.1.2. Content Server

1.1.3. Audio Client

1.1.4. Controller

1.1.5. AV Receiver

1.2. Operation

1.2.1. Initialization of Content Server and Audio Client

1.2.1.1. Initialization of Audio Client

1.2.1.1.1. Search for Content Server

1.2.1.1.2. Connection with Content Server

1.2.1.1.3. Transmission of Client Information

1.2.1.2. Initialization of Content Server

1.2.1.2.1. Response to Content Server Search

1.2.1.2.2. Accepting Command Port Connection

1.2.1.2.3. Accepting Push Port Connection (Case 1)

1.2.1.2.4. Accepting Push Port Connection (Case 2)

1.2.2. Main Operation of Content Server and Audio Client

1.2.2.1. Accepting Command

1.2.2.1.1. Command Allocation Processing

1.2.2.1.2. Status Notification Command Processing

1.2.2.1.3. Server Request Issuing Command Processing

1.2.2.2. Normal Reproducing

1.2.2.2.1. Obtaining Music List

1.2.2.2.2. Specifying Music Piece

1.2.2.2.3. Reproducing Music Piece

1.2.2.3. Special Reproducing

1.2.2.3.1. Fast Forward Reproducing

1.2.2.3.2. Fast Reverse Reproducing

1.2.2.3.3. Pause

1.2.2.3.4. Slow Reproduction

1.2.3 Operation of Controller

1.2.3.1 Connection with Content Server

1.2.3.1.1 Obtaining Monitoring Handle and Control Handle

1.2.3.2 Monitoring Function

1.2.3.3 Control Function

1.2.3.3.1. Control Command Processing

1.2.3.3.2. Reproducing Control

1.2.3.3.3. Determine if in Reproducible Format and Reproduce

1.2.3.3.4. Continuous Reproducing Control

1.2.3.3.5. Continuous Reproducing Control Using List Construction Key

1.2.3.3.6. Continuous Reproducing Control with Priorities

1.2.3.3.7 Continuous Reproducing Control Using Control Handle

1.2.3.3.8. Continuous Reproducing Control by Content Server

1.2.3.3.9. Continuous Reproducing Control by Audio Client Itself

1.2.3.3.10. Continuous Reproducing Control Using Reproducing InstructionManagement Table

1.2.4. AV Receiver Control

1.2.5. Firmware Updating

2. Other Embodiments

2.1. Audio Client Stored in Outlet Box

2.2. Obtaining Music Data on Internet

2.3. Reproducing with Function of Changing Obtaining Data Length

2.4. Skip Reproducing

2.5. Repeating Reproducing

2.6. Midway Reproducing

2.7. Client with Automatic Connection Recovery Function

1. Preferred Embodiment

1.1. Configuration

1.1.1. General Configuration

Referring to FIG. 1, the network type audio system 10 according to anembodiment of the invention includes a plurality of content servers Sito Si for storing music data for a large number of music pieces, aplurality of audio clients C1 to Cj for reproducing music based on musicdata from the content servers S1 to Si, a plurality of controllers A1 toAk for controlling and monitoring the audio clients C1 to Cj, AVequipment AVR (such as an AV receiver including a switch and anamplifier), and an AVR client AC for controlling the AV receiver AVR.Hereinafter, as each representative one of them, the content server Si,the audio client Cj, and the controller Ak will be described.

Herein, music data is stored in the content server Si, but the musicdata and/or video data may be stored instead. Alternatively, variousother kinds of digital contents (for example, still pictures such asphotographs) may be stored. In the following, music data will bedescribed by way of illustration. There are a plurality of contentservers Si, audio clients Cj, and controllers Ak in the following, butat least one such content server or audio client is necessary. Whenthere are a plurality of content servers S1 to Si, the audio client Cjmay obtain music data from any of the content servers S1 to Si or mayobtain music data only from one particular content server Si. Thecontroller Ak does not have to be provided at all. A plurality of AVreceivers AVR or AVR clients AC may be provided while they do not haveto be provided at all.

They are connected with one another through a LAN (Local Area Network)12, but USB, IEEE 1394 or anything suitable for building up a computernetwork may be employed. When a LAN is employed, the standard TCP/IPprotocol for personal computers (PCs) is preferably selected, while theUDP protocol may be employed. In other words, the protocol is notparticularly limited. In FIG. 1, the content servers or the audioclients are connected to branch from the main wiring of a LAN, but for10BASE-T or 100BASE-TX, for example, they are connected in a star shapehaving a hub in the center.

1.1.2. Content Server

Referring to FIG. 2, each of the content servers Si includes an HDD(hard disc drive) 14 for storing compressed digital music data, a CPUprocessing portion 20 including a database management portion 16 and anetwork protocol processing portion 18, and a LAN controller 22 thattransmits/receives signals between the content server Si and the LAN 12.

1.1.3. Audio Client

Referring to FIG. 3, each of the audio clients Cj includes amicrocomputer processing portion 28 including a network protocolprocessing portion 24 and a system operation portion 26, a flash memory30, a memory 32 that temporarily stores and sequentially outputssequentially input, compressed digital music data or the like, an audiosound processing portion 34 that decodes compressed digital music dataand generates non-compressed digital music data, a D/A converter (DAC)36 that converts digital music data into analog music data, and a LANcontroller 38 that transmits/receives signals between the audio clientCj and the LAN 12. Unlike the content server Si, the audio client Cjdoes not have to include an HDD for storing compressed digital musicdata.

1.1.4. Controller

Referring to FIG. 4, the controllers Ak each include an input device 301such as a keyboard, a mouse, a tablet, and a touch panel, a display 302such as a liquid crystal display and a CRT (Cathode Ray Tube), a CPU 303that executes prescribed processing according to installed computerprograms, and a LAN controller 304 that transmits/receives signalsbetween the controller Ak and the LAN 12. The controllers A1 to Akfunction as clients to the content servers S1 to Si similarly to theaudio clients C1 to Cj. The controller Ak is different from the audioclient Cj in that the audio client Cj has a reproducing function, whilethe controller Ak functions mainly for monitoring and controlling theaudio client rather than reproducing.

The audio client mainly has a reproducing function but may havemonitoring and controlling functions as well. In this case, the audioclient also functions as a controller.

1.1.5 AV Receiver

The AV receiver AVR is connected to an AVR client AC for example byEIA-232 though not specifically limited. The AVR client AC mainly has acommunicating function with the AV receiver AVR, but it may have areproducing function as well similarly to the audio client Cj.

1.2. Operation

1.2.1. Initialization of Content Server and Audio Client

Referring to FIG. 5, when an audio client is powered, the audio clientsearches for a content server (S11). A content server in operation amongthe plurality of content servers Si connected to the LAN 12 responds tothe search (S21).

Then, the audio client issues a connection request to the content serverin order to enable transmission/reception of data with the contentserver (S12). The content server establishes connection with the audioclient in response to the connection request (S22).

Finally, the audio client transmits various client information relatedto the audio client to the content server (S13), and the content serverreceives the information (S23).

When the above initialization is completed, the process proceeds to thenext operation of obtaining the music list. Before describing theoperation, the initialization operation of the audio client will bedescribed in detail.

1.2.1.1. Initialization of Audio Client

1.2.1.1.1. Search for Content Server

Referring to FIG. 6, the audio client clears the server list forrecording the IP address and port number of a found content server(S1101).

The audio client then broadcasts a predetermined magic word through acommand port for example by the UDP protocol (though not specified) ontothe LAN 12 (S1102). If there is a content server Si in operation amongthe content servers connected to the LAN 12, the content server receivesthe broadcast magic word at a search port and returns the same magicword to the audio client that has broadcast the magic word together withserver specifying information (specifically its IP address and portnumber) to specify itself.

The audio client then resets the timer to count time for receiving theserver specifying information (S1103) and then determines whether theserver specifying information is received (S1104).

If the server specifying information is received (if a content server isfound), the audio client records the server specifying information inthe server list (S1105). The audio client then determines whether theserver list is filled (S1106). If the list is filled, the searchingoperation is complete, and otherwise the process returns to step 1103.

Meanwhile, if the server specifying information is not received (if nocontent server is found), the audio client determines whether or notprescribed time such as two seconds has passed before the serverspecifying information should have been received (S1107). If the timehas not elapsed, the process returns to step S1104. More specifically,the audio client waits for a response from any content server for twoseconds.

If the two seconds have passed before the server specifying informationshould have been received, the audio client determines whether or notthe server list is empty (S1108). If the server list is empty, in otherwords, if no server specifying information is recorded in the serverlist, the audio client returns to step S1102 and once again broadcaststhe magic word. Meanwhile, if the server list is not empty, in otherwords, if server specifying information on at least one content serveris recorded, the audio client ends the searching operation. Morespecifically, the audio client continues to search until it finds atleast one content server.

As the result of searching for the content server, an IP address and aport number corresponding to one or more content servers are provided tothe server list.

1.2.1.1.2. Connection with Content Server

Referring to FIG. 7, the audio client selects one content server in theserver list in response to the user's operation (S1201) and obtains theIP address and port number of the selected content server (S1202).

The audio client generates a TCP (Transmission Control Protocol) socket(1) using the obtained IP address and the command port (S1203) andconnects the content server with the TCP socket (1) (S1204). The commandport is a port used to transmit/receive commands between the contentserver and the audio client. If the content server successfully acceptsconnection with the command port (S2201) and the connection isestablished, the process proceeds to step S1206, and otherwise theconnection is not successful (S1205). In this way, the audio clientestablishes the connection to transmit/receive commands between thecontent server and itself.

The audio client then transmits a client index request command to thecontent server by the TCP socket (1) (S1206). The content serverresponds to the client index request command and returns a client indexto the audio client from the TCP socket (1) (S2202), and the audioclient receives the index (S1207). The client index is an ID numberallocated to each audio client by the content server. The client indexrequest command is a command by which the audio client requests thecontent server to transmit a client index.

The audio client then generates a TCP socket (2) using the IP addressand push port of the content server (S1208) and establishes connectionwith the content server by the TCP socket (2) (S1209). The push port isa port in a stand-by state so that the port can always receive avoluntary request from the content server or a request from the contentserver in response to a request from a controller. Hereinafter, theserequests from the content server are referred to as “server requests.”If the content server successfully accepts the connection through thepush port (S209), and the connection is successfully established, theprocess proceeds to step S1211, but otherwise the connection is notsuccessful (S1210). In this way, the audio client establishes theconnection to receive a server request.

At this point, the content server is not informed of which audio clientis connected to the push port. Therefore, the audio client transmits theclient index obtained in step S1207 to the content server by the TCPsocket (2) (S1211). The content server specifies the audio clientconnected to the push port based on the client index. Thereafter, thecontent server uses the push port for transmitting a server request tothe audio client.

In this way, the two kinds of connection are established through thecommand port and the push port. These two kinds of connection areestablished not only between the audio client Cj and the content serverSi but also between the controller Ak (that will be described) and thecontent server Si, and between the AVR client AC and the content serverSi.

In the server-client system in general, as with the HTTP protocol, acontent server returns a response (such as an HTML document) to arequest (such as a page request) from a client. This means that only theclient has a trigger for action, and the content server cannotvoluntarily act upon the client. Therefore, when the content servertakes any voluntary action to a client such as notifying the client thatthe content server will be shut down, for example, such notificationcannot be carried out unless there is a request from the client.

A command to check for a server request is issued to the content serverat prescribed intervals so that the client can receive a server requestif there is any. The content server responds to the command issued bythe client to transmit a server request to the client and the clientreceives the request.

It is known that in the case of the HTTP protocol, any dynamicallyupdated page must be reloaded for every prescribed time period. This canbe called obtaining a server request by polling by a client, but themethod suffers from the following disadvantages.

(1) Unless the polling intervals are short enough to frequently checkfor a server request, there could be time difference between when thecontent server issues a request and when the audio client actuallyreceives the request.

(2) However, if the polling intervals are short as described above, thenetwork traffic and the server-client load increase.

(3) The frequency of how often the content server has to transmit aserver request to the client is lower than the normal frequency oftransmitting/receiving a command, so that most of the polling occasionsare wasted because the inquiry about the presence/absence of a serverrequest usually ends up with the answer “absence.”

In order to solve these disadvantages, a server request may betransmitted to the client by interrupt by the content server rather thenthe polling by the client. In this manner, the lack of real time-ness inthe above (1) and the unnecessary load such as that in the above (2) and(3) can be eliminated.

To this end, the two kinds of connection are established. One isconnection formed at a command port through which the audio client Cjissues a command and the content server Si responds to the command. Theother is connection formed at the push port through which the contentserver Si sends a server request to the audio client Cj. In this manner,without having to carry out polling by the audio client Cj, the contentserver Si can notify the audio client Cj of a server request.

Now, the operation using these two kinds of connection will be describedin detail.

As shown in FIG. 8, the content server Si notifies all the audio clientsCj of shutting down through the push port when it shuts down and causesthe audio clients Cj to carry out some operation (such as turning offthe power).

As shown in FIG. 9, when the controller Ak controls the audio client Cj(for example to reproduce or stop), the controller Ak transmits arequest to the content server Si to issue a server request including thecontrol content through the command port. The content server Si respondsto the command to transmit a server request to the audio client Cjthrough the push port. Consequently, the controller Ak can control theaudio client Cj.

As shown in FIG. 10, the audio client Cj transmits a change in itsoperation state to the content server Si through the command port. Thecontent server Si transmits the change in the operation state throughthe push port to the controller Ak that monitors the operation state ofthe audio client Cj. Therefore, the audio client Cj can notify thecontroller Ak of a change in its operation state in real time.

As described above, the network traffic and the load on the contentserver and audio client in the network type audio system can beminimized, so that the performance of the entire system can beincreased.

1.2.1.1.3 Transmission of Client Information

Referring to FIG. 11, the audio client transmits its attributeinformation to the content server (S1301 to S1303) and transmits itsinitial status (S1304 and S1305).

More specifically, the audio client transmits the audio client type bythe TCP socket (1) (S1301). The audio client type includes the kind of areproducible music format, whether it can be operated by a remotecontroller (remote), the presence/absence of an EIA-232 port and thelike.

The audio client then transmits its product ID by the TCP socket (1)(S1302). The product ID is machine information provided for each ofaudio client types. Therefore, the audio clients of the same type areprovided with the same product ID.

The audio client then transmits the firmware ID by the TCP socket (1)(S1303). The firmware ID is the version information of firmwareinstalled in the audio client.

The audio client then transmits the initial volume value by the TCPsocket (1) (S1304). The initial volume value is an initial value for thevolume of sound reproduced by the audio client.

Finally, the audio client transmits the initial status of the audioclient by the TCP socket (1) (S1305). The initial status of the audioclient includes a stop status or the like.

The content server receives client information transmitted from a clientand stores the received information in client information database (FIG.13). The client information is transmitted not only from the audioclient Cj but also from the controller Ak and the AVR client AC to thecontent server Si. The content server Si controls all the clients basedon the client information.

1.2.1.2. Initialization of Content Server

Now, the initialization of a content server corresponding to theinitialization of the audio client will be described.

Referring to FIG. 12, the content server secures storage regions for theclient information database as shown in FIG. 13 as many as the maximumnumber of clients and clears them (S201). The client information eachincludes a flag indicating the presence/absence of connection, the typeof the client, the present status, the present volume value, a productID, a firmware ID, the name of the client, a reproducing file name, anda list construction key.

As the client type, the type such as an audio client, a controller, andan AVR client, and a reproducible data format (such as MP3 and WAV) arerecorded. For the client type, whether or not it can be controlled witha remote is also recorded. If the audio client can be remote-controlled,information as being “remote-controllable” is recorded. The status to berecorded includes “reproducing,” “stop,” “pause,” “complete,” and“firmware in the process of updating.” As the reproducing file name, thefull path name of the HDD 14 that stores the data of the music piecebeing reproduced at present is recorded. The reproducing file name doesnot have to be the file name itself such as a full pathname but may beany information that can be used to specify the file. For example, atable having prescribed ID numbers and file names in association witheach other may be stored in the content server, and the content servermay refer to the table to convert an ID number into a corresponding filename. In this way, long file names do not have to betransmitted/received. Since the file storing the data of a music piececannot be specified directly based on the file name, it is alsoadvantageous in terms of security. In addition, the list constructionkey is used by the content server to produce a list, which will bedetailed later.

The content server then produces sockets to accept connection requeststo the command port and the push port and a server search request to thesearch port (S202). The search port is a port used when a content serveris searched for, and the content server monitors to check whether or nota magic word is input to the search port.

Then, the content server builds up a content information database asshown in FIG. 14 and a firmware information database as shown in FIG. 15(S203). The content information database includes content informationpieces as many as the number of music pieces. The content information ofeach music piece includes a file name, the title of the piece, an artistname, an album title, a genre, the length (time) of the piece, a dataformat, the number of how many times it has been reproduced, and thelast accessed time. The file name includes the full path of the HDD 14that stores the data of the music piece of interest. The firmwareinformation database includes firmware information pieces as many as thenumber of firmware files. The firmware information includes a productID, a firmware ID, a file size, a data format, and a file name. As thefile name, the full path name indicating the site on the Internet wherethe firmware is stored is recorded.

If something is written in the search port (S204), the content servercarries out response processing to the content server search that willbe described (S205). The content server also carries out command portconnection accepting processing that will be described (S207), ifsomething is written in the command port (S206). The content servercarries out push port connection accepting processing (case 1) that willbe described (S209), if the push port is written (S208). The contentserver carries out the push port connection accepting processing (case2) that will be described (S211), if a push port yet to be processed iswritten (S210).

1.2.1.2.1. Response to Content Server Search

Referring to FIG. 16, when something is written in the search port, thecontent server obtains the written content (S2051) and determineswhether or not the content is a correct magic word (S2052). If thecontent is a correct magic word, the content server returns the samemagic word to the source client (S2053) together with the IP address andport number of the content server.

1.2.1.2.2. Accepting Command Port Connection

Referring to FIG. 17, when a connection request is issued from a clientto the command port, the content server determines whether or not thenumber of presently connected clients has reached the maximum clientnumber (S2071). If the number of presently connected clients has reachedthe maximum client number, the content server searches for a client witha low priority and forcibly disconnects the found client (S2072). Thepriorities of the clients are lower for audio clients not in the processof reproducing at present and audio clients that have not communicatedfor prescribed time. The content server clears the client information ofthe forcibly disconnected client (S2073).

Alternatively, the content server may be adapted not to connect withfurther clients if the number of clients connected at present hasreached the maximum client number.

If there are more sockets to be connected with clients, or if moreconnectable sockets are secured by disconnecting clients with lowpriorities, the content server starts to accept connection requests fromclients (S2074).

When a request is successfully accepted (S2075), the content serversearches for an empty region in the client information database (S2076).More specifically, the content server searches for client informationwhose flag indicates FALSE. The content server allocates the foundregion as a new client information storage region (S2077) and clears theprevious client information (S2078).

The content server then sets the flag to TRUE (S2078), and socketinformation obtained as the result of accepting the request is stored inthe socket field of the client information storage region (S2079).

1.2.1.2.3. Accepting Push Port Connection (Case 1)

Referring to FIG. 18, if a client requests connection to the push port,the content server starts to accept the request (S2091). If the requestis successfully accepted (S2092), socket information obtained as theresult of accepting the request is stored in a queue for a push port yetto be processed (S2093). At the point, the content server still cannotspecify the client connected to the push port. Such a push port isreferred to as “unprocessed push port.”

1.2.1.2.4. Accepting Push Port Connection (Case 2)

Referring to FIG. 19, if the client issues a connection request to anunprocessed push port, the content server obtains a command written inthe push port (S2111). If the command has a size larger than zero(S2112) and is a client index notification command (S2113), the contentserver determines whether or not the client indicated by the clientindex has already been connected to the command port (S2114).

If connection is not complete, the content server sets the error code to−1 (failure) (S2115) and proceeds to step S2119. Meanwhile, ifconnection is complete, the content server registers the push port asthe push port for the client (S2116). The content server furthereliminates the push port from the queue for unprocessed push ports(S2117) and sets the error code to zero (success) (S2118). The contentserver then returns the set error code to the client (S2119).

1.2.2. Main Operation of Content Server and Audio Client

1.2.2.1. Accepting Command

Referring back to FIG. 12, the content server accepts a command from aclient after completing the initialization. More specifically, thecontent server repeats steps S213 to S217 as many times as the maximumclient number (S212, S218, S219). The character n is a client index fromzero to the maximum client −1 allocated to a client.

More specifically, the content server refers to the flags in the clientinformation database and determines whether or not the n-th client hasalready been connected to the command port (S213). If it has alreadybeen connected, the content server determines whether or not data hasbeen written to the command port for the n-th client (S214). If data hasbeen written, the content server determines whether or not the size ofthe written data is 0 or −1 (S215). If the data is 0 or −1, which meansthat a client is disconnected or there is a socket error, the contentserver clears the client information of the n-th client (S216).Meanwhile, if otherwise, the content server carries out the followingcommand processing (S217).

1.2.2.1.1. Command Allocation Processing

Referring to FIG. 20, if data has been written to the command port by aclient, the content server branches processing in response to a commandstored in the head four bytes (S2171). More specifically, if the commandis a status notification command to notify a change in the status to thecontent server from the audio client (S2172), the controller is notifiedof the status transmitted from the audio client (S2173), details ofwhich will be described later. If the command is a content serverrequest issuing command from the controller to the audio client (S2174),the audio client is notified of the request from the controller (S2175),details of which will be described later. In addition, the contentserver carries out prescribed processing in response to the command.

1.2.2.1.2. Status Notification Command Processing

Referring to FIG. 21, when a command from an audio client (hereinafterreferred to the “audio client of interest”) is a status notificationcommand, the content server stores client information such as a statusand volume stored in parameters in the command in the client informationdatabase (S21731). Therefore, the content server always holds the mostupdated version of client information.

The content server then searches for a controller among all the clientsand notifies the found controller of the status of the audio client ofinterest. Therefore, the content server repeats the following stepsS21733 to S21736 as many times as the maximum client number (S21732,S21737, S21738).

More specifically, the content server refers to the client type of theclient information and determines whether or not the n-th client is acontroller (S21733). Therefore, the status of the audio client ofinterest can be prevented from being notified to any other audio clientthat is not a controller. If the client is a controller, the contentserver determines whether or not the controller has a monitoring handlefor the audio client of interest (S21734). If the controller has themonitoring handle, the content server determines whether or not theconnection between the controller and the push port is established(S21735).

If the connection to the push port is established, the content serverwrites the client information of the audio client of interest in thepush port of the controller and thus notifies the controller of thestatus of the audio client of interest (S21376).

1.2.2.1.3. Server Request Issuing Command Processing

If a command from a controller is a server request issuing command, asshown in FIG. 22, the content server obtains information such as thesource controller, the destination audio client, the request content andthe like included in the command (S21751).

The content server determines whether or not the source controller hasthe control handle (that will be described) for the destination audioclient (S21752). If the source controller does not have the controlhandle, the error code is set to −1 (S21753). Therefore, a controllerwithout the control handle can be prevented from controlling the audioclient.

If the controller has the control handle, the content server refers tothe flag in the client information and determines whether or notconnection is established at the command port of the destination audioclient (S21754). If the connection is not established, the error code isset to −2 (S21755). Therefore, the command can be prevented from beingtransmitted to an uncontrollable audio client.

If the connection is established at the command port of the destinationaudio client, the content server determines whether connection isestablished at the push port of the destination audio client (S21756),and if the connection is not established, the error code is set to 1(S21757). Meanwhile, if the connection is established, the contentserver transmits the content of the request from the controller to thepush port of the destination audio client (S21758) and sets the errorcode to 0 (no error) (S21759).

Finally, the content server returns the error code to the sourcecontroller (S21760).

Note that if the destination audio client is not connected to the pushport, the content of the request from the controller may be transmittedto the destination audio client in response to an inquiry by pollingfrom the destination audio client.

1.2.2.2 Normal Reproducing

Now, the operation of how the user has a desired music piece reproducedby the audio client Cj will be described. Here, the user does notdirectly specify the desired piece but specifies a list of desired musicpieces and selects a desired music piece in the list.

Referring to FIG. 23, an audio client transmits a music list requestcommand in response to the user's operation (S14). The music listrequest command is a command from the audio client to request thecontent server to provide a list of desired music pieces. The music listincludes the titles of music pieces, the artists' names, and the like.The content server transmits a music list to the requesting audio clientin response to the music list request command (S24), and the audioclient receives the list (S14).

The audio client responds to the user's operation to specify a musicpiece included in the music list (S15), and the content server preparesfor distribution of the specified music piece accordingly (S25).

The content server distributes the specified music piece to the audioclient (S26), and the audio client reproduces the distributed musicpiece (S16). The audio client then stops reproducing the music piece atthe end of reproduction or in response to the user's operation (S17).

Now, each of steps S14 to S16 will be described in detail.

1.2.2.2.1. Obtaining Music list

Referring to FIG. 24, the audio client determines whether or not torequest the content server to provide a play title list (S1401). Theplay title list includes the titles of palylists. The palylist is a listof music pieces selected by the user. The content server stores aplurality of palylists produced by the user.

When the user tries to select one of the plurality of palylists storedin the content server, the user requests the content server to provide aplay title list in order to check what kind of palylists are registered.The audio client requests the content server to provide a play titlelist in response to the user's operation and receives the play titlelist from the content server (S1402).

Then, the audio client determines whether or not to request for aspecified palylist (S1403). If the user specifies a desired palylist inthe play title list, and the audio client requests for the specifiedpalylist in response to the operation, the process proceeds to S1413,and otherwise the process returns to step S1401 or S1403 (S1404).

If the play title list is not requested, the audio client determineswhether or not to request the content server to provide an artist list(S1405). The artist list includes a plurality of artists' names. Theartist list is not prepared in the content server, but such a list isproduced from the content information database shown in FIG. 14 everytime there is a request from the audio client.

If the user requests for an artist list, the audio client requests thecontent server to provide a desired artist list in response to theuser's operation and receives the artist list from the content server(S1406).

The audio client then determines whether or not to request for a musiclist by the specified artist (S1407). If the user specifies a desiredartist in the artists' list, and the audio client requests for a musiclist by the specified artist in response to the operation, the processproceeds to step S1413, and otherwise the process returns to step S1401or S1407 (S1408). The music list includes the titles of music pieces bythe specified artist and the like, and the music list is not prepared inthe content server as with the artist list as described above and it isproduced from the content information database shown in FIG. 14 everytime there is a request from the audio client.

If no artist list is requested, the audio client determines whether ornot to request the content server to provide a genre list (S1409). Thegenre list includes a plurality of genres. The genre list is notprepared in the content server as with the artist list either and it isproduced from the content information database shown in FIG. 14 everytime there is a request from the audio client.

If the user requests for a genre list, the audio client requests thecontent server to provide a desired genre list in response to the user'soperation and receives the genre list from the content server (S1410).

The audio client then determines whether or not to request a music listin a specified genre (S1411). If the user specifies a desired genre inthe genre list, and the audio client requests a music list in thespecified genre in response, the process proceeds to step S1413, andotherwise the process returns to step S1401 or S1411 (S1412). The musiclist including the titles of music pieces in the specified genre is notprepared in the content server as with the artist's music list and it isproduced from the content information database shown in FIG. 14 everytime there is a request from the audio client.

Consequently, when a music list is requested, the audio client requeststhe content server to provide the music list and receives the music listfrom the content server (S1413). In this way, the music list issuccessfully obtained.

Now, referring to FIG. 25, the operation of obtaining a genre list,selecting pop music as a desired genre, and obtaining a pop music listwill be described.

In this case, the audio client transmits a list request command torequest the content server to provide a genre list (S1421) and thecontent server returns the genre list accordingly (S2401). The audioclient receives the genre list from the content server and stores thelist in the memory 32 as shown in FIG. 26 (S1422).

The genre list may be prepared and stored in the content server, buthere the list is produced from the content information database shown inFIG. 14 every time there is a request from the audio client. Now, howsuch a genre list is produced will be described.

As shown in FIG. 27, in the case that the content server stores n musicpieces, the content information database has n records. Each recordincludes the title of a music piece, the genre, the artist's name, andthe album title.

If a genre list is produced using the content information database, asshown in FIG. 28, the content server initializes the index representingthe record number to zero (S24011).

Then, the content server determines whether or not the genre of therecord indicated by the index already exists in the genre list (S24012).If there is no such genre, the content server adds the genre of therecord to the genre list (S24013) and then increases the index (S24014).Meanwhile, if there is the genre in the list, the content server skipsstep S24013 and directly increases the index (S24014).

The content server then determines whether or not the record numberindicated by the index is smaller than the number n of all the records(S24015). If the number is smaller, the process returns to step S24012,and otherwise the genre list is complete.

By the above processing, the content server picks up the genres of allthe music pieces stored in the content information database withoutduplication and produces a genre list. In this way, the genre list isnot formed into a database in advance and temporarily produced everytime the audio client requests for one, so that a memory region toconstantly store the genre lists is not necessary.

Referring back to FIG. 25, the genre list thus produced is transmittedfrom the content server to the audio client (S2401, S1422). The userselects a desired genre (pops in this example) in the genre list. Theaudio client requests the content server to provide a music list in thegenre selected in response to the user's operation (S1423). The contentserver returns the music list in the genre selected in response to therequest from the audio client to the audio client (S2402). The audioclient receives the music list from the content server and stores thelist in the memory 32 in FIG. 29 (S1424).

Similarly to the genre list described above, the music list is notprepared in advance in the content server but is produced based on thecontent information database shown in FIG. 27. More specifically, thecontent server produces a music list every time the audio clientrequests for one. Now, the method of producing the music list will bedescribed in conjunction with FIG. 30.

The content server initializes the index indicating the record number inthe content information database shown in FIG. 27 to zero (S24021).

The content server then compares the genre of the record indicated bythe index to the selected genre (pops in this example) and determineswhether or not they match (S24022). If they match, the content serveradds the title, the artist's name, the album title and the like in therecord to the music list (S24023) and then increases the index (S24024).Meanwhile, if they do not match, the content server skips step S24023and directly increases the index (S24024).

The content server then determines whether or not the record numberindicated by the index is smaller than the number n of all the records(S24025). If the number is smaller than n, the process returns to stepS24022, and otherwise the music list is complete.

By the above processing, the content server picks up music pieces onlyin the selected genre from the content information database and producesa music list. In this way, the music list is not included in a databasein advance but is temporarily produced every time the audio clientrequests for one, so that a memory region to constantly store the musiclists is not necessary.

Note that when a music list is produced, music pieces in irreproducibledata formats may be omitted rather than picking up all the correspondingmusic pieces. Alternatively, rather than producing a music list inresponse to every request from the audio client, music lists may becached once they are produced. In this case, a memory region to storethe music lists is necessary, but a music list can immediately bereturned in response to a request from the audio client.

Similarly to the genre list described above, the entire music list isnot sent at a time but is transmitted gradually piece by piece. Morespecifically, the steps of requesting a music list (S1423, S1425),returning the music list (S2402, S2403), and receiving the music list(S1424, S1426) are repeated. Now, the operation will be described indetail.

The audio client transmits a list request command as shown in FIG. 31 tothe content server (S1423). The list request command is a command torequest the content server to provide a list and includes an obtainingstart index, an obtaining number, and a list construction key. Theobtaining start index is an index to indicate the first music piece tobe obtained by the audio client among the music pieces included in theselected genre list. The obtaining number is the number of music piecesto be obtained by the audio client. The list construction key that willbe described includes the kind of a filter indicating a category ofinterest when music pieces are extracted from the content informationdatabase, and a specific keyword classified into the category. Althoughnot specified, in this example, the obtaining start index=0, theobtaining number=50, and the list construction key is set as “genre(kind of filter)=pops (keyword).”

The content server responds to the list request command and returnssearch result data as shown in FIG. 32 to the audio client (S2402). Thesearch result data includes part of the music list, an effective number,and the remaining number. The effective number is the number of musicpieces actually returned by the content server to the audio client. Theremaining number is the number of music pieces remaining after the musiclist is returned to the audio client. In this example, in response tothe list request command in which the obtaining start index=0, and theobtaining number=50, the content server returns the first to the 50-thmusic pieces in the produced music list to the audio client (S2402).Assuming that the number of all the music pieces in the music list is110, then the effective number=50, and the remaining number=60(=110−50).

Since there are the music list for still 60 music pieces remaining inthe content server, the audio client again transmits a list requestcommand to the content server (S1425). This time, the obtaining startindex=51, and the obtaining number=50.

The content server responds to the list request command and againreturns search result data to the audio client (S2403). Here, theeffective number=50, and the remaining number=10(=110−(50+50)). Morespecifically, the content server again returns a music list for 50 musicpieces to the audio client (S2403). The audio client receives the musiclist and stores the list in the memory 32 (S1426).

Note that in the above example, since the number of all the music piecesin the music list=110, and the obtaining number=50, the 50 music piecesforming part of the music list are returned. Meanwhile, when the numberof all the music pieces in the music list is smaller than the obtainingnumber, for example when the number of all the music pieces in the musiclist=40, and the obtaining number=50, all the music pieces in the musiclist, i.e., 40 pieces are returned.

In the above example, the obtaining start index=0, and therefore themusic pieces are returned starting from the first piece in the list,while if for example the obtaining start index=10, the music pieces arereturned from the 11th piece in the music list. In this case, the numberof all the music pieces in the music list=110, and in the first listrequest command, the obtaining starting index=10, and the obtainingnumber=50. The content server returns search result data in which theeffective number=50 and the remaining number=50(=110−10−50).

If the number of music pieces that can be stored in the memory 32 islarger than the number of all the music pieces in the list, the audioclient can store the entire music list. However, the capacity of thememory 32 is considerably smaller than that of the content server, andtherefore the audio client can usually store only a part of the musiclist in the memory 32.

According to the above embodiment, the audio client downloads the musiclist in divided forms from the content server. Therefore, when a regionfor storing at least 50 music pieces is secured in the memory 32 in theaudio client, the music list for all the 110 pieces can be downloaded.Therefore, the capacity of the memory 32 may be small.

For example as shown in FIG. 33A, if the audio client stores the musiclist for 50 pieces in the memory 32, and then the user desires to obtainthe 51st music piece and on, the audio client moves the last half of themusic list to the first half of the memory 32 as shown in FIG. 33B.Then, as shown in FIG. 33C, the audio client stores a music list for 25music pieces from the 51st in the last half of the memory 32.

The audio client repeats the above operation and receives the entiremusic list or receives only the music pieces as many as the number thatcan be stored in the memory 32.

In the example shown in FIG. 25, a genre is selected, and then a musicpiece in the genre is immediately selected. Meanwhile, as shown in FIG.34, a genre may be selected, then an album in the genre may be selected,and then a music piece may be selected from the album.

In this case, the audio client requests the content server to provide analbum list in the genre selected in response to the user's operation(S1427). The content server returns the album list in the genre selectedin response to the request from the audio client to the audio client(S2404). The audio client receives the album list from the contentserver and stores the list in the memory 32 (S1428).

The audio client then requests the content server to provide a musiclist for an album selected in response to the user's operation (S1429).The content server returns the music list for the album selected inresponse to the request from the audio client to the audio client(S2405).

1.2.2.2.2 Specifying Music Piece

Referring to FIGS. 35 and 36, the audio client requests the contentserver to provide information on a specified music piece (S1501), thecontent server returns information on the specified music piece inresponse to the request to the audio client (S2501), and the audioclient receives the information (S1502).

More specifically, the audio client transmits a music piece informationrequest command as shown in FIG. 37 (S1501). The music piece informationrequest command includes the file name of the specified music piece. Thecontent server responds to the music piece information request commandand returns music piece information as shown in FIG. 38 (S2501). Themusic piece information includes the data offset and data size of thespecified music piece. Music data for example in the form of MP3generally has header information preceding the content information. Thedata offset is used to skip the header information and specifies thestart address of the music piece. The content server analyzes theoffset, so that the audio client does not have to analyze the offset.The content server generally has greater processing capability than theaudio client does, and therefore the system as a whole can be increasedin the processing speed. The data size is used to check the ending timeof the music piece.

The audio client then requests the content server to prepare forreproducing the specified music piece (S1503). The content serverresponds to the request to open the file of the specified music pieceand returns the result to the audio client (S2502), and the audio clientreceives the result (S1504).

More specifically, the audio client transmits a music piece reproducingpreparation command as shown in FIG. 39 (S1503). The music piecereproducing preparation command includes the file name of the specifiedmusic piece and the list construction key that will be described. Thecontent server responds to the music piece reproducing preparationcommand to open the file and returns an error code as shown in FIG. 40(S2502). As for the error code, an error is present if for example acorresponding file does not exist and file transfer cannot be prepared,while an error is not present if such preparation can be carried out. Ifthere is an error, prescribed error processing is carried out (S1504).

1.2.2.2.3. Reproducing Music Piece

Then, the audio client requests the content server to transfer musicdata in a specified range in the music data of the specified music piece(S1601), and the content server responds to the request to return themusic data in the specified range to the audio client (S2601). The audioclient receives and stores the music data in the memory 32 (S1602).

More specifically, the audio client transmits a music piece datatransfer request command as shown in FIG. 41 (S1601). The music piecedata transfer request command includes the obtaining start address andthe obtaining data length of the music data to be transferred. As shownin FIG. 42, the content server returns the music data for the obtainingdata length from the start address specified by the obtaining startaddress (S2601). The size of data to be transmitted at a time ispreferably in the range from 1 Kbytes to 32 Kbytes though not specified,more preferably 4 Kbytes to 16 Kbytes. The content server can reduce theload more as the data volume is smaller. The audio client can processthe data more quickly as the data volume to receive at a time is larger.Meanwhile, the range of 1 Kbytes to 32 Kbytes (especially from 4 Kbytesto 16 Kbytes) is the optimum range for both the content server and theaudio client. The data size is previously set on the audio client side.

The obtaining start address is sequentially increased by the obtaineddata length that has been transferred and the operation is repeated(S1605, S2603, S1606, S1607, S2604, S1608), so that the music data cansequentially be transferred by each specified range.

In this way, the audio client can obtain music data in a specified rangefrom the content server, so that a music piece can be reproduced frommidway, or the music piece can be reproduced in a flexible mannerincluding fast forward reproducing, fast reverse reproducing, and slowreproducing in response to the user's operation.

The memory 32 includes a plurality of buffers (eight buffers in theexample shown in FIG. 43). As shown in FIG. 44, the audio client obtainsmusic data for one buffer from the start of a music piece using a musicpiece data transfer request command and stores the data. As shown inFIG. 45, the audio client continues to obtain and store music data inthe same manner until all the buffers are filled with data.

Once all the buffers are filled with data as described above during theprocess from steps S1601 to S1608, the audio client starts to outputmusic data to a sound processing portion 34 from the first buffer asshown in FIG. 46.

When the audio client starts to output music data as described above andreproduces the music, the audio client transmits a reproducing status tothe content server (S1603). The content server receives the status andreturns an error code to the audio client (S2602). The audio clientchecks the error code and carries out prescribed error processing ifthere is an error (S1604).

As described above, when music is reproduced while the music datathereof is being transferred, an empty space is created for one bufferwith time as shown in FIG. 47. The presence of the empty buffer (S1609)causes the audio client and the content server to again carry out theabove described transfer operation (S1610, S2605, S1611). As a result,as shown in FIG. 48, the empty buffer is filled. The audio client andcontent server repeat the transfer operation every time there is anempty buffer (S1612 to S1616, S2606, S2607).

Note that in the above example, music data starts to be output after allthe buffers are filed with music data, but the data may start to beoutput before all the buffers are filled.

The audio client then determines whether or not the entire music data ofthe specified music piece has been received based on the size of thedata obtained in step S1502 (S1617). If the entire data has beenreceived, the audio client determines whether or not the specified musicpiece has been reproduced to the end based on the received music data(S1671). If the music piece has been reproduced to the end, the audioclient transmits a stop or completion status to the content server(S1618). When the user operates the audio client to reproduce aspecified music piece and the audio client finishes reproducing thepiece or when the user operates the audio client to stop reproducing themusic piece midway, the audio client transmits a stop status. Meanwhile,when the user operates the controller, and the audio client reproduces amusic piece specified by the controller to the end in response, theaudio client transmits a completion status. The reason why there are thestop status and completion status will be described later.

The content server receives any of these statuses and returns an errorcode to the audio client (S2608). The audio client checks the error codeand carries out prescribed error processing if there is an error(S1619).

As described above, music data is divided and intermittently transferredfrom the content server to the audio client, music can correctly bereproduced with a smaller buffer capacity.

In the above example, music data is transferred on a byte basis, but MP3music data is preferably transferred on a frame basis. This is becausethe frame-based transfer is advantageous in terms of time display andspecial reproducing such as fast forward or fast reverse reproducing(that will be described). Therefore, the audio client requests musicdata in the MP3 form on a frame-basis. In response to the request, thecontent server searches for the frame header of MP3 in the specifiedfile and transfers the frame from its start. Since the header includes aparameter for calculating the data length, it is not difficult to findthe starts of the following frames once the header is found.

1.2.2.3. Special Reproducing

The audio client carries out the following processing before a series ofprocessing steps including transfer request for music data and returningand obtaining the data so that the special reproducing such as fastforward reproducing, fast reverse reproducing, pause, and slowreproducing can be carried out.

1.2.2.3.1. Fast Forward Reproducing

Referring to FIG. 49, in fast forward reproducing, the audio clientmonitors for a key input (S1620) and sets a skip amount to a valuegreater than zero in response to the pressing of the fast forwardreproducing key (S1621) and otherwise sets the skip amount to zero(S1622).

When there is an empty buffer (S1609), the audio client calculates theobtaining start address of music data according to the followingexpression (S1624).

Obtaining start address=previous obtaining start address+obtaining datalength+skip amount

If the fast forward reproducing key is not pressed in step S1620, theskip amount is set to zero in step S1622, and therefore the obtainingstart address increases by the obtaining data length. In this case, theaudio client continuously obtains music data, normal reproducing iscarried out. Meanwhile, the fast forward reproducing key is pressed instep S1620, the skip amount is set to a value greater than zero in stepS1621, and therefore the audio client skips music data for the skipamount and obtains the data. In this way, the audio client carries outfast forward reproducing. In this example, when the skip amount is setto the value equal to the obtaining data length, double-speed fastforward reproducing is carried out. If the skip amount is twice as largeas the obtaining data length, triple-speed fast forward reproducing iscarried out.

1.2.2.3.2 Fast Reverse Reproducing

In fast reverse reproducing, the audio client determines whether or notthe fast reverse reproducing key has been pressed in place of step S1620described above and sets the skip amount to a value which is smallerthan zero and whose absolute value is greater than the previousobtaining data length in place of step S1621 described above. This isbecause if the absolute value of the skip amount is smaller than theprevious obtaining data length, the obtaining range of music dataoverlaps. If the obtaining data length is the same each time, and theabsolute value is set to be twice as large as the obtaining data length,reverse reproducing can be carried out at normal reproducing speed.

The audio client determines whether or not the obtaining start addresscalculated in step S1624 is within the range of the music data (S1625).If the address is within the range, the audio client proceeds to thenext step S1610, while otherwise the audio client stops reproducing. Fornormal reproducing, the end of the music data is detected, and thereforesuch ending condition is not necessary. However, for the fast reversereproducing in particular, the start of the music data must be detected,and the ending condition must be satisfied. Note however that ratherthan providing the ending condition, the file of the next music piecemay be opened for fast forward reproducing or the file of the previousmusic piece may be opened for fast reverse reproducing.

Note that for MP3 music data, once the frame header is read, the headerof the next frame can be located virtually without fail as describedabove. Therefore, a certain number of frames may be skipped, then datafor the following several frames may be reproduced, and then severalframes may be skipped again. The process may be repeated, so that fastforward reproducing can be carried out.

1.2.2.3.3. Pause

Referring to FIG. 50, as for pause, the audio client monitors for a keyinput (S1626, S1628) and sets to the operation status to pause inresponse to the pressing of the pause key (S1627), while the audioclient sets the operation status to reproducing in response to thepressing of the reproducing key (S1629).

When there is an empty buffer (S1609), the audio client determineswhether or not the operation status is set to pause (S1631). If thestatus is set to the pause, the audio client returns to step S1626 anddoes not start to transfer the next music data. Meanwhile, if the statusis not set to the pause, in other words, if the reproducing key has beenpressed so that the pause is off, and the operation status has changedto reproducing, the audio client proceeds to step for request and thenext music data starts to be transferred.

If the operation status is set to the pause, the audio client stopsreading from the buffer. This is because the previously transferredmusic data still remains in the buffer.

1.2.2.3.4. Slow Reproducing

For motion pictures instead of music, slow reproducing may be necessary.Motion picture files are normally in a compressed form such as MPEG-2,and therefore the audio client includes a decoder to reproduce suchdata. For the slow reproducing, in response to a command to cause thedecoder to carry out slow reproducing, video data stored in the buffersreduces at lower speed. For slow reproducing at 30% of the normalreproducing speed, the amount of video data read out from the buffer bythe decoder per unit time is 30% as well. Therefore, the audio clientwaits for an empty buffer to be generated for a longer period in stepS1609, so that slow reproducing can be carried out.

1.2.3. Operation of Controller

1.2.3.1. Connection with Content Server

The controller Ak establishes connection with the content server Sisubstantially in the same manner as the audio client Cj.

Referring to FIG. 51, once the controller Ak is turned on, thecontroller Ak connects to the command port of the content server Si(S3001). The controller Ak issues a client index request command throughthe command port (S3002). The content server Si responds to the commandto return a client index to the controller Ak, and the controller Akstores the obtained client index (S3003).

Then, the controller Ak connects to the push port of the content serverSi (S3004). The controller Ak issues a client index notification commandthrough the push port and transmits the client index stored in stepS3003 to the content server (S3005). In this way, the push port is madeopen (S3006).

The controller Ak then notifies the content server Si about the clienttype through the command port (S3007). Here, unlike the audio client Cjdescribed above, the controller Ak notifies about the client type ofitself, i.e., its being a controller. The content server Si candistinguish the audio client Cj from the controller Ak based on theclient type.

The controller Ak then obtains the client information of the audioclient Cj from the content server Si (S3008) and displays the status andthe like included in the information on the monitor.

The controller Ak requests for the monitoring handle and control handleof the audio client Cj connected to the content server Si based on theclient type and the obtained client index and obtains the handles(S3009).

The above connection process is different from that of the audio clientCj in that the controller Ak notifies the content server Si of its ownclient type, in other words, its being a controller. Another differenceis that the controller Ak obtains the monitoring handle and/or thecontrol handle, which will be detailed.

1.2.3.1.1. Obtaining Monitoring Handle and Control Handle

Referring to FIG. 52, the controller Ak displays the list of all theaudio clients Cj connected to the content server Si (S30091). Thecontroller Ak selects an audio client Cj to be monitored in the list inresponse to the user's operation (S30092). The audio client CJ to bemonitored in response to the user's operation is selected only when thenetwork type audio system is activated for the first time. For thesecond time and on, it is preferable that the audio client Cj selectedfirst that is registered is automatically selected.

The controller Ak then transmits the client index of the selected audioclient Cj to the content server Si and requests for its monitoringhandle (S30093). The content server Si stores the client index of thesource controller Ak and the received client index of the audio clientCj in association with each other (S20001) and issues a monitoringhandle to the source controller Ak (S20002). In this way, the controllerAk obtains the monitoring handle of the selected audio client Cj(S30094).

The controller Ak then responds to the user's operation to select theaudio client Cj to be controlled in the list (S30095). The controller Akthen transmits the client index of the selected audio client Cj to thecontent server Si and requests for its control handle (S30096). Thecontent server Si stores the client index of the source controller Akand the received client index of the audio client Cj in association witheach other (S20003) and issues the control handle to the sourcecontroller Ak (S20004). In this way, the controller Ak obtains thecontrol handle for the selected audio client Cj (S30097).

The monitoring handle represents the authority provided from the contentserver Si to the controller Ak to monitor the audio client Cj. In thisway, when the status of the audio client Cj changes, the new statusafter the change is notified to the content server Si. The contentserver Si transmits the client information of the audio client Cj to thecontroller Ak from time to time through the push port, and thecontroller Ak responds to the information to update the clientinformation of the audio client Cj.

In this network type audio system, the larger the number of audioclients Cj is, the greater the load is upon the LAN 12. The transmissionof commands from the controller Ak, the status of the audio client Cjand the like affects the traffic on the LAN 12.

As shown in FIG. 53, when there are a number of controllers A1 to A3 onthe same LAN 12, the content server Si can transmit all the clientinformation on the audio clients C1 to C3 to all the controllers A1 toA3, but this could increase the network traffic and the load imposedupon the content server.

Therefore, as shown in FIG. 54, the controller A1 obtains the monitoringhandle only for the audio client C1, and the controller A2 obtains themonitoring handle only for the audio client C2, so that the contentserver Si transmits the client information of the audio client C1 onlyto the controller A1 and the client information of the audio client C2only to the controller A2.

The content server Si transmits the client information only to thecontroller Ak that has the monitoring handle for the audio client Cj,and therefore the network traffic and the load upon the content servercan be reduced. Meanwhile, the controller A3 may obtain the monitoringhandles for all the clients C1 to C3, so that the content server Si maytransmit the client information to all the controllers A1 to A3.

Meanwhile, the control handle represents the authority provided by thecontent server Si to the controller Ak to control the audio client Cj.

In the network type audio system, if there are a number of controllersAk, and any of the controllers Ak can control an audio client Cj, in theprocess of reproducing a music piece by an audio client Cj in responseto a command from a controller Ak, another controller Ak may instructthe same audio client Cj to stop reproducing or reproduce another musicpiece.

Therefore, in this system, only the controller Ak that has the controlhandle for an audio client Cj can control the audio client Cj. Anycontroller Ak without the control handle for an audio client Cj cannotcontrol the audio client Cj.

If the content server limits the number of controllers that can obtaincontrol handles, combinations of the audio client and controllers thatcan control audio clients can be arranged. When a controller issues acontrol handle release command to the content server, the controller cangive up control handle.

1.2.3.2. Monitoring Function

As described above, the controller Ak can monitor the audio client Cj byobtaining the monitoring handle.

Referring to FIG. 55, the controller Ak requests the content server Sito provide client information (S31), the content server Si responds tothe request to return the client information (S27), and the controllerAk obtains and stores the information (S31). Alternatively, if thecontent server Si receives client information from an audio client Cj,the content server Si transmits the client information to the controllerAk through the push port, and the controller Ak obtains and stores theinformation. The controller Ak then displays the obtained clientinformation (S32). Now, the monitoring function by the controller willbe detailed.

Referring to FIG. 56, the content server Si responds to a request fromthe controller Ak or client information received from an audio clientand transmits the client information to the controller Ak (S2701). Thecontroller Ak searches into the received client information for changesin the information. More specifically, the controller checks the clientindex (S3101) and stores to which audio client Cj the client informationbelongs. The stored product ID and firmware ID of the audio clients arechecked (S3102, S3103).

More specifically, the kind of the audio client is determined based onthe product ID, and the version of the firmware is determined based onthe firmware ID. If the version of the firmware applied to the audioclient is out of date, the controller Ak accesses the customer serviceon the Internet and has the firmware distributed to the audio client Cjfor automatic updating. How to update the firmware will be detailedlater.

Note that the controller Ak analyzes the received client information tocheck the client type, branches to processing for the audio client Cj ifthe client type suggests the audio client Ci, and otherwise ignores theinformation.

The controller Ak then checks for a change in the connection information(S3104) and changes the display of the connection state with the audioclient Cj if there is a change (S3105).

Therefore, the controller Ak can constantly monitor if the plurality ofaudio clients Cj are turned on and connected to the content server Si.

If an audio client Cj is connected, the controller Ak checks for achange in the volume value (S3106) and changes the display of the volumevalue if there is a change (S3107).

The controller Ak then checks for a change in the list construction key(that will be detailed)(S3108) and requests the content server Si toprovide a music list using the list construction key if there is achange (S3109). The content server Si responds to the request to returnthe music list (S2702), and the controller Ak receives the music list(S3110).

The controller Ak stores the received music list as the list of musicpieces in the process of being reproduced by the audio client Cj, checksfor the order of the presently reproduced music piece in the sequence ofthe music list and stores the ordinal number (S3111).

The controller Ak then checks for a change in the music piece in theprocess of being reproduced (S3112). If there is a change, thecontroller Ak checks the data format of the music piece (S3113), changesthe display of the title of the music piece being reproduced or thedisplayed name of the artist (S3114), checks the order of the presentlyreproduced music piece in the sequence of the music list and stores theordinal number (S3115).

Finally, the controller Ak checks for a change in the status (S3116) andchanges the displayed status if there is a change (S3117). If the audioclient Cj is remote-controlled, the controller Ak monitors and displaysthe status. When the status of the audio client Cj is a completionstatus (S3118), the controller Ak instructs the audio client Cj tocontinue to reproduce the next music piece (S3119). The continuousreproducing will be detailed later.

The above processing is repeated every time there is a change in theclient information of any of the audio clients whose monitoring handlesare obtained by the controller.

Although not shown, the controller Ak monitors for the client type ofeach of the audio clients Cj. The controller Ak also monitors for thedata format that can be reproduced by the audio client and displays onlythe titles of music pieces that can be reproduced.

As in the foregoing, when the content server receives client informationfrom a client, the client information is forcibly transmitted to acontroller Ak through a push port, so that the controller can constantlymonitor the audio clients Cj, and only the minimum necessary informationis transmitted from the content server Si to the controller Ak.Therefore, the load of processing imposed upon the controller Ak can bereduced. When there are a plurality of audio clients Cj, the controllerAk can distinguish the audio clients Cj based on the client indexes andcan update the client information in real time.

1.2.3.3. Control Function

The controller Ak obtains the control handle as described above in orderto control the audio client Cj.

Referring to FIG. 57, the controller Ak transmits a control command tothe content server Si (S33), and the content server Si transmits thecommand to a specified audio client Cj (S28). The audio client Cjoperates in response to the control command, changes its status (S18),and transmits the new status to the content server Si (S19). The contentserver Si transmits the status to the controller Ak (S29), and thecontroller Ak changes the status of the stored client information inresponse (S34).

1.2.3.3.1. Control Command Processing

Now, referring to FIG. 58, the processing carried out by the audioclient Cj in response to a control command received from the controllerAk through the content server Si will be described.

When some data is written in the push port (S3001), the audio client Cjreceives and analyzes the data (S3002).

When the received data is a reproducing command (S3003), the audioclient Cj obtains the specified file name from the content server Si(S3004). The audio client Cj specifies the title of the music piece, thealbum, the genre and the like based on the obtained file name. The audioclient Cj then specifies the music piece and instructs the contentserver Si to transfer the music data of the piece (S3005). The audioclient Cj reproduces the music piece based on the transferred musicdata.

If the received data is a reproducing stop command (S3006), the audioclient Cj stops issuing the music piece data transfer request command,which stops transfer of the music data (S3007), and transmits a stopstatus to the content server Si (S3008). The audio client Cj alsoresponds to a volume value set command, a pause command, an AV receivercontrol command, a firmware update command and the like to carry outprescribed processing (S3009 to S3010).

1.2.3.3.2. Reproducing Control

Now, the operation of the controller Ak to have a desired piece by adesired artist reproduced by the audio client Cj using a reproducingcommand will be described.

Referring to FIG. 59, the controller Ak checks for connection with anaudio client Cj (S3011) and checks the firmware ID and product ID of theaudio client Cj if there is the connection (S3012, S3013).

The controller Ak then determines whether or not the audio client Cj isan audio client or an AVR client based on the client type (S3014). Sinceit is the audio client Cj in this example, the controller Ak determineswhether or not the music list by the desired artist has been obtained(S3015). If the list has not been obtained yet, the controller Akobtains the music list by the desired artist from the content server Si(S3016). The controller Ak displays the music list at the display.

When there is a music piece the user desires to reproduce in theobtained music list (S3017), the controller Ak selects the music piecein response to the input operation of the user and transmits areproducing command to the content server Si (S3018). The reproducingcommand includes the name of the file that stores the data of theselected music piece and the audio client index of the audio client thatis to reproduce the music piece. Meanwhile, if there is no desired musicpiece, the controller Ak obtains the next music list by the desiredartist (S3016).

The content server Si specifies the audio client Cj based on the clientindex transmitted from the controller Ak and transmits the file name ofthe selected music piece to the audio client Cj (S28).

The audio client Cj responds to the reproducing command transmittedthrough the content server Si from the controller Ak to reproduce adesired music piece and changes the status to the reproducing status(S18). The audio client Cj transmits the reproducing status to thecontent server Si (S19), and the content server Si transmits thereproducing status to the controller Ak (S29). The controller Ak changesthe status of the audio client Cj to the reproducing status in response(S34).

1.2.3.3.3. Determine if in Reproducible Format and Reproduce

A music list includes music pieces in all the formats regardless ofwhether or not music in the formats can be reproduced by the audioclient Cj. Therefore, if the controller Ak directly displays a musiclist obtained from the content server Si in response to the user'sselection of desired music pieces, the following problem can arise.

When the user selects a music piece in a format that cannot bereproduced by the audio client Cj, and the controller Ak instructs theaudio client Cj to reproduce the music piece selected by the user, nosound is reproduced while the reproducing state is displayed at theaudio client Cj.

Therefore, as shown in FIG. 60, information related to the reproducibleformats is added to the client type in the client information. In thisway, the client type includes information related to the hardwarestructure of the client and the formats that can be reproduced by theaudio client.

The information related to the hardware structure includes the followingitems. The “audio client (intelligent type)” can reproduce music andreceive a remote signal. The “audio client (non-intelligent type)” canreproduce music but cannot receive a remote signal. The “controller” isa client that can monitor and control an audio client through thecontent server. The “AVR client” has an EIA-232 port and can communicatewith an AV receiver. The “AVR controller” is a client that can controland monitor an AVR client through the content server. Informationrelated to the reproducible formats include MP3, WAV, and WMA and so on.

The client type of one client may include information related to aplurality of hardware structures in some cases and information relatedto a plurality of reproducible formats in other cases.

Now, the process of how the controller Ak displays a music list to theuser will be described in conjunction with FIG. 61.

The controller Ak determines whether or not the audio client Cj toreproduce a music piece is connected to the content server Si (S3501).If not connected, the audio client Cj cannot reproduce the music piece,and therefore all the music pieces in the music list are displayed asirreproducible music pieces or the music pieces are not displayed at all(S3502). In this way, the user can be prevented from selecting any piecethat cannot be reproduced by the audio client Cj.

Meanwhile, if the connection is established, the following steps S3505to S3507 are repeated as many times as the number of music pieces in themusic list (S3503, S3504, S3508).

More specifically, the controller Ak determines whether or not theformat of the n-th piece in the music list is reproducible by the audioclient Cj (S3505). If the format is reproducible, the controller Akdisplays the piece as a reproducible piece (S3506). Meanwhile, thecontroller Ak displays the piece as an irreproducible piece or does notdisplay it at all if the format is not reproducible (S3507).

If for example the audio client C1 can reproduce both MP3 and WAV, thecontroller Ak displays all the music pieces in the music list (palylistin the example) as shown in FIG. 62. If however the audio client C2 canreproduce MP3 but not WAV, music pieces in the MP3 format are alldisplayed normally but those in the WAV format are displayed pale incolor as shown in FIG. 63. Alternatively, they do not have to bedisplayed at all rather than being displayed pale in color. In this way,the user can be prevented from selecting a music piece in the WAV formatthat cannot be reproduced by the audio client C2.

Note that when the connection state or the client type of the audioclient Cj is changed, the controller Ak displays the music list all overagain and the present client information of the audio client can bedisplayed in real time.

Now, the operation of the controller Ak when the user operates thecontroller Ak to have a music piece reproduced by the audio client Cjwill be described.

Referring to FIG. 64, if the user selects a music piece desired to bereproduced, the controller Ak determines whether or not the format ofthe selected music piece is reproducible by the audio client Cj (S3511).More specifically, the controller Ak compares the format of the selectedpiece to the reproducible formats in the client type.

If the format is reproducible, the controller Ak instructs the audioclient Cj to reproduce the selected music piece (S3512). Meanwhile, ifthe format is not reproducible, the user is notified that the audioclient Cj cannot reproduce the selected music piece (S3513).

As in the foregoing, music pieces that can be reproduced by the audioclient Cj are displayed distinctly to the user, so that the user can beprevented from selecting a music piece that cannot be reproduced by theaudio client Cj.

1.2.3.3.4. Continuous Reproducing Control

When the user operates the audio client Cj to reproduce a music piece,the audio client Cj can continuously reproduce music pieces in thealready obtained music list. If however the audio client Cj reproduces amusic piece based on the instruction from the controller Ak, the audioclient Cj does not have the music list and therefore the controller Akmust instruct the audio client Cj to reproduce the next music piece sothat the audio client Cj continues to reproduce the music pieces in themusic list.

If there is only one controller on the network, there is no problem, butif there are a number of controllers, the audio client may not normallyreproduce music pieces in a continuous manner. If for example thecontent server that has been notified of the completion of reproducingby the audio client notifies the completion to all the controllers, theaudio client receives instructions for continuous reproducing from theplurality of controllers. This problem is even more complicated whenthere are a plurality of content servers on the network. Therefore, inorder to carry out continuous reproducing by the controller in thenetwork type audio system, which controller to instruct continuousreproducing to a client must be managed.

According to the embodiment, the audio client Cj reproduces a musicpiece in response to a instruction from a controller Ak and transmits acompletion status upon finishing reproducing, while otherwise forexample when the audio client Cj independently reproduces a music piecein response to the user's operation and finishes reproducing it, orstops reproducing the music piece midway in response to the user'soperation, a stop status different from the completion status istransmitted. When the completion status is received, the controllerdetermines that continuous reproducing processing should be carried out,selects the music piece following the previously selected music piece inthe music list, and instructs the audio client to reproduce the nextmusic piece. When the stop status is received, the controller does notinstruct the audio client to reproduce the next music piece.

As described above, the audio client transmits the completion status andthe stop status in the different manners depending upon situations, sothat the controller can determine whether or not to instruct the audioclient to reproduce the next music piece based on the received status.

Consequently, when the audio client Cj stops reproducing a music piecemidway in response to the user's operation, or the audio client Cjselects a music piece on its own and finishes reproducing it, a stopstatus is transmitted to the controller through the content server.Therefore, the controller can be prevented from erroneously instructingthe audio client to reproduce the next music piece.

When there are a plurality of controllers, the content server that hasreceived a completion status from the audio client transmits thecompletion status and the stop status to each of the controllers indifferent manners. More specifically, referring to FIG. 65, when thecontroller A1 instructs the audio client C1 to reproduce a music piece,the controller A1 first transmits a reproducing command directed to theaudio client C1 to the content server Si. The content server Si receivesthe reproducing command from the controller A1 and transmits thereceived command to the audio client C1. The audio client C1 receivesthe reproducing command from the content server Si and starts toreproduce the music piece.

Referring to FIGS. 66 and 67, the audio client C1 finishes reproducingthe music piece, and then transmits a completion status to the contentserver (S1901). The content server Si then receives it (S2901). Then,the content server Si repeats the following steps S2903 to S2906 as manytimes as the number of clients (S2902, S2907).

The content server Si determines whether or not the n-th client is acontroller that has a monitoring handle for the audio client C1 based onthe client-index n (S2903).

If the client is the controller that has a monitoring handle, thecontent server Si determines whether the n-th client (controller) is thecontroller A1 that has instructed the audio client C1 to reproduce themusic piece (S2094).

If the client is the controller A1 that has instructed the audio clientC1 to reproduce the music piece, the content server Si transmits thecompletion status received from the audio client C1 to the controller Al(S2905), and the controller A1 receives it (S3401). Meanwhile, if theclient is a controller A2 instead of the controller A1 that hasinstructed the audio client C1 to reproduce the music piece, the contentserver Si transmits a stop status instead of the completion statusreceived from the audio client C1 to the controller A2 (S2906) and thecontroller A2 receives it (S3402).

Referring to FIG. 68, the controller A1 selects the music piece the nextto the previously selected piece in the music list in response to thereceived completion status and transmits a reproducing command to causethe audio client C1 to reproduce the music piece to the content serverSi (S3403). The content server receives the command and transmits thecommand to the audio client C1. The audio client C1 reproduces the nextmusic piece in response to the reproducing command transmitted from thecontent server Si.

Meanwhile, the controller A2 receives the stop status, determines thatthe audio client C1 is in a stop state, and does not carry outcontinuous reproducing processing as opposed to the controller A1.

The audio client Cj transmits to the content server Si a reproducingstatus when the status changes to reproducing, a pause status when thestatus changes to pause, and a stop status when a music piece specifiedby the audio client Cj has been reproduced to the end. Meanwhile, when amusic piece specified by the controller Ak has been reproduced to theend, the audio client Cj transmits a completion status to the contentserver Si.

As in the foregoing, the statuses transmitted to the controller Ak whenthe audio client Cj finishes reproducing a music piece are separatedinto the stop status and the completion status. Therefore, thecontroller Ak can determine whether the audio client Cj instructed bythe controller to reproduce has finished reproducing a music piece.Consequently, the controller Ak can determine whether to instruct theaudio client Cj to continue reproducing or simply to display the stopstatus from the audio client Cj.

Note that when the audio client Cj finishes reproducing a music piece,the status to be notified to the content server Si may be differentbetween when the music piece has been reproduced in response to aninstruction from a dedicated remote and when the music piece has beenreproduced in response to an instruction from the controller Ak that hasboth the monitoring and control handles. This is because the dedicatedremote that has only the control handle cannot receive a status from thecontent server Si and therefore cannot carry out continuous reproducingprocessing.

1.2.3.3.5. Continuous Reproducing Control Using List Construction Key

The controller Ak obtains various music lists from the content serverSi, selects a music piece in the lists, and has the music piecereproduced by the audio client Cj. The controller Ak monitors for thestatus of the audio client Cj, selects the next music piece in theobtained music list once the audio client Cj finishes reproducing theselected music piece, and has the music piece reproduced by the audioclient Cj. In this way, the controller Ak controls the audio client Cjto continuously reproduce music pieces. In order to instruct reproducingof succeeding music pieces, the music list must be stored in advance.Therefore, the power supply for the controller Ak that instructsreproducing of music pieces cannot be turned off during reproducing amusic piece.

Therefore, the following method is employed so that the controller Akcan instruct the audio client Cj to carry out continuous reproducingeven when the power supply for the controller Ak that has instructed theaudio client Cj to reproduce is turned off during reproducing.

When the user desires to select a music piece to be reproduced from thecontent information database, the user uses various music lists inselecting a piece such as the music list of a certain artist or in acertain genre. A list construction key is defined so that an arbitrarymusic list can be produced based on the content information database.The list construction key is added to the client information asinformation used by the audio client Cj to specify the music list whosemusic piece is presently reproduced.

Referring to FIG. 69, the list construction key includes a filter kindand a key word. The filter kind is used to specify which category in thecontent information database is based in producing a music list, anexample of which is shown in FIG. 70. If the filter kind is “TITLE=,”“GENRE=,” “ARTIST=,” “ALBUM=,” or “FILENAME=,” music pieces whose title,genre, artist name, album title, or file name matches a keyword aresearched in the content information database and the found pieces areformed into a music list. If the filter kind is “PLAYLIST=,” musicpieces registered in a palylist whose file name matches the keyword aresearched in the content information database and the found pieces areformed into a music list.

For a music list for the artist name “xxxx” for example, the filter kindis “ARTIST=,” the keyword is “xxxx” and therefore the list constructionkey is “ARTIST=xxxx.” When “*” (asterisk) is specified as the keyword, alist by a keyword that can be used for the filter kind is produced. Alist produced by the list construction key “ARTIST=*” is a list by thename of an artist whose music pieces are registered in the contentinformation database.

Now, the process of continuous reproducing processing by a controller toan audio client that has finished reproducing a piece specified by thecontroller will be described.

Referring to FIG. 71, the audio client Cj instructed by the controllerAk to reproduce a music piece transmits a completion status to thecontent server Si upon finishing reproducing the music piece. Thecontent server Si transmits client information including the completionstatus, the file name of the reproduced music piece, and the listconstruction key to the controller Ak in response to the change in thestatus of the audio client Cj.

The controller Ak starts to carry out client information displayprocessing as shown in FIG. 56 in response to the received clientinformation. The processing has already been described above, andtherefore hereinafter the continuous reproducing control using the listconstruction key will mainly be described.

The controller Ak checks for a change in the list construction key(S3108) and obtains a music list whose piece is reproduced at present bythe audio client Cj using the list construction key if there is a changein the key (S3110). More specifically, the controller transmits thereceived list construction key to the content server, and the contentserver produces a list based on the list construction key and transmitsthe produced list to the controller. Once the power supply is turnedoff, and the controller Ak no longer stores the music list whose pieceis being reproduced by the audio client Cj, the music list beingreproduced is obtained from the content server Si using the listconstruction key obtained after connection with the content server Si.

In this example, since the status changes to the completion status, thecontroller Ak carries out completion processing (S3119). Morespecifically, the controller Ak selects the music piece the next to thepiece the audio client Cj has finished reproducing in the music list andinstructs the audio client Cj to reproduce the selected music piece.

Referring to FIG. 72, the completion processing will be detailed. Thecontroller Ak increases the reproducing music number n stored in stepS3111 in FIG. 56 (S31191) and thus specifies the music piece toreproduce next. Then, the controller Ak determines whether or not thereproducing music number n is equal to or smaller than the number ofmusic pieces in the music list (S31192). If the reproducing music numbern is more than the number of music pieces in the music list, thecontroller Ak determines that the audio client Cj has reproduced themusic list the end and sets the reproducing music number n to 1(S31193), and the music piece to reproduce next returns to the firstmusic piece in the list.

If the reproducing music number n is not more than the number of musicpieces in the music list, the controller Ak checks whether or not then-th music piece is in the format that can be reproduced by the audioclient Cj (S31194), and if the format is reproducible, the controllerinstructs the audio client Cj to reproduce the n-the music piece in themusic list (S31195). If the format is not reproducible, the completionprocessing is recursively carried out in order to reproduce the musicpiece the next to the next music piece. The controller Ak instructs theaudio client Cj to skip the irreproducible music piece and reproduce thenext music piece.

As in the foregoing, when the power supply for the controller Ak isturned off after the audio client Cj is instructed to reproduce a musicpiece, the controller Ak loses the music list at the time of instructingthe audio client Cj. However, when the power supply is turned on again,and connection with the content server is established, as described inconnection with step S3008 in FIG. 51, the controller Ak obtains theclient information of the audio client Cj from the content server Si.The client information includes the list construction key, and thereforethe controller Ak can obtain the music list presently reproduced by theclient Cj again based on the list construction key. Therefore, if thepower supply for the controller Ak is turned off after the audio clientCj is instructed to reproduce a music piece, the audio client Cjfinishes reproducing the music piece and transmits a completion status.When the controller Ak receives the completion status, the controllercan instruct the audio client Cj to reproduce the next music pieceaccording to the regained music list.

Note that in order to stop the reproducing operation of the audio clientCj, the controller Ak needs only transmit a stop command to the audioclient Cj through the content server Si. In this case, the stop statusis returned from the audio client Cj to the controller Ak through thecontent server Si. In order to temporarily stop the reproducingoperation of the audio client Cj, the controller Ak needs only transmita pause command to the audio client Cj through the content server Si. Inthis case, the pause status is returned from the audio client Cj to thecontroller Ak through the content server Si.

1.2.3.3.6. Continuous Reproducing Control with Priorities

The embodiment will be described particularly in connection with thecontent server S1 and the audio client C1. According to the embodiment,a controller management table is stored in the HDD 14 of the contentserver S1. An example of the controller management table is shown as thefollowing Table 1. In the controller management table, priorities incontrolling the audio client C1 are registered in association with thecontroller indexes provided to the controllers A1 to Ak. TABLE 1controller management table priority controller 1 A1 2 A2 3 4 . . . . .. k

According to the embodiment, computer programs to carry out the stepsshown in FIG. 73 are installed in the content servers S1 to Si, theaudio clients C1 to Cj, and the controllers A1 to Ak. The operation ofthe network type audio system 10 according to the embodiment will bedescribed with reference to the flowchart in FIG. 73.

To start with, the controller A1 requests connection to the contentserver S1, and the connection between the controller A1 and the contentserver S1 is established when the request is accepted by the contentserver S1 (S30301).

Subsequently to the controller A1, the controller A2 requests connectionto the content server S1, and the connection between the controller A2and the content server S1 is established when the request is accepted bythe content server S1 (S30401).

Meanwhile, the content server S1 records the controller index of thecontroller A1 in association with the “first” priority and thecontroller index of the controller A2 in association with the “second”priority in the controller management table (S20101). Consequently, thecontroller management table as shown in Table 1 is obtained. Accordingto the controller management table, the controller A1 has the authoritywith the highest priority about continuous reproducing processing, andthen the controller A2 has the authority with the second highestpriority about the continuous reproducing processing.

Now, the operation of how the controller A1 instructs the audio clientC1 to continuously reproduce a plurality of music pieces through thecontent server S1 will be described.

The controller A1 requests the content server S1 to provide a music listto be continuously reproduced (S30302). More specifically, thecontroller transmits a list construction key necessary for producing themusic list to the content server S1.

When the user selects a music piece desired to be reproduced from thecontent server S1, she/he selects various music lists in selecting amusic piece such as a music list of a certain artist and a music list ina certain genre. As shown in FIG. 69, the list construction key is asearch key to extract music pieces from the content server S1 andarbitrarily produce such a music list. The list construction key is madeof two parameters, a filter kind and a keyword.

The filter kind is used to specify the category of a music piece to beentered to the music list, and a specific example is shown in FIG. 70.

The content server S1 produces a music list based on the listconstruction key transmitted from the controller A1 and transmits thelist to the controller A1 (S20102).

More specifically, when the filter kind is “TITLE=,” “GENRE=,”“ARTIST=,” “ALBUM=,” or “FILENAME=,” one or more music pieces whosetitle, genre name, artist name, album title, or file name matches akeyword are searched, and the matching one or more pieces are formedinto a music list. If the filter kind is “PLAYLIST=,” music piecesregistered in a palylist whose file name matches the keyword aresearched and the matching pieces are formed into a music list(palylist). The content server S1 registers the list construction key inassociation with the client index (the ID information of the audioclient C1) as one kind of client information related to the audio clientC1.

The controller A1 instructs the audio client C1 to reproduce a musicpiece specified in response to the user's operation in the obtainedmusic list through the content server S1 (S30303). The audio client C1responds to the reproducing instruction from the controller A1 torequest the content server S1 to provide the music content of thespecified music piece (S10201). The content server S1 distributes themusic content requested by the audio client C1 to the audio client C1(S20103). The audio client C1 starts to reproduce the music piece basedon the music content transmitted from the content server S1 (S10202).

When the audio client C1 finishes reproducing a specified music piece,the audio client C1 transmits a completion status indicating thecompletion of reproducing to the content server S1 (S10203). The contentserver Si refers to the controller management table 104 as shown in FIG.74 upon receiving the completion status from the audio client C1,transmits the completion status as it is to the controller A1 with thehighest priority and transmits a stop status different from thecompletion status to the controller A2 with a lower priority (S20104).

As shown in FIG. 74, the controller A1 instructs the audio client C1 tocontinuously reproduce the next music piece in the music list throughthe content server S1 (S30304). The audio client C1 reproduces the nextmusic piece in response to the continuous reproducing instruction fromthe controller A1. Then, the audio client C1 repeats step S201 and theoperation thereafter. Meanwhile, the controller A2 does not take apositive action in response to the stop status received from the contentserver S1 and simply monitors the state of the audio client C1.

Note that when the controllers A1 to Ak are disconnected from thecontent server S1, the content server S1 updates the controllermanagement table 104. More specifically, the controller index of thecontroller disconnected from the content server S1 is deleted, and thepriorities of the controller indexes of the controllers with lowerpriorities than the deleted index are sequentially advanced. For exampleas shown in FIG. 75, when the controller A1 with the highest priority isdisconnected from the content server S1, the controller A2 with thesecond highest priority is advanced to replace the controller A1 andobtains the authority about the continuous reproducing processing.

In the above described example, the controller A1 instructs reproducingfirst, and then the same controller A1 instructs continuous reproducing.Meanwhile, if the controller A2 instructs reproducing first, thecontroller A1 instructs continuous reproducing as long as the controllerA1 has the highest priority. In this case, the controller A1 does nothave a music list if it receives the completion status from the contentserver S1. Therefore, the controller A1 obtains the music list from thecontent server S1 using the list construction key of the audio client C1registered in the content server S1 and specifies the next music pieceaccordingly.

All the music pieces included in the music list are not always stored inthe single content server S1 and may be stored in a plurality of contentservers such as the content servers S1 and Si in some cases. In thiscase, the audio client C1 reproduces music pieces in the content serverS1 and then must reproduce music pieces in the separate content serverSi. Therefore, after reproducing the music pieces in the content serverS1, the audio client C1 must disconnect from the content server S1 andhas to connect to the content server Si, in other words, serverswitching processing is carried out.

The audio client C1 connected to the content server Si responds to areproducing instruction from the controller A1 to request the contentserver Si to provide the music content of the specified music piece, andthe content server Si distributes the requested music content to theaudio client C1.

The audio client C1 finishes reproducing the music piece and thentransmits a completion status to the content server Si. The contentserver Si, upon receiving the completion status, refers to thecontroller management table inside and transfers the completion statusto the controller with the highest priority and a stop status to thecontrollers with lower priorities.

Here, the control management table in the content server Si may be thesame as or different from the controller management table in the contentserver S1. In order that a plurality of content servers use the samecontroller management table, for example a certain content server maydetermine the priorities in the controller management table, andtransfer the controller management table to the other content servers.Meanwhile, in order that a plurality of content servers use differentcontroller management tables, the content servers each independentlydetermine the priorities in a controller management table.

As described above, according to the embodiment, the content server S1,upon receiving the completion status from the audio client C1, refers tothe controller management table, transmits the completion status only tothe controller A1 with the highest priority, and the stop status to theother controller A2. Therefore, only the controller A1 with the highestpriority instructs continuous reproducing and the other controller A2does not. Consequently, the possibility of competition betweencontinuous reproducing instructions can be eliminated, and continuousreproducing processing can normally be carried out.

The priorities are determined based on the order of connection with thecontent server S1 in the above embodiment, but they may be determined inother manners such as based on the order of issuing an instruction tothe audio client C1. The plurality of content servers do not have to beprovided, and at least one content server is necessary. The plurality ofaudio clients do not have to be provided either, and at least one audioclient is necessary.

1.2.3.3.7. Continuous Reproducing Control Using Control Handle

According to the embodiment, computer programs to carry out the stepsshown in FIG. 76 are installed in the content servers S1 to Si, theaudio clients C1 to Cj, and the controllers A1 to Ak. Similarly to theabove described embodiment, this embodiment may be applied to a networktype audio system including the plurality of controllers A1 to Ak, andat least one content server or audio client is necessary.

Unlike the above-described embodiment, according to this embodiment,control handle management tables are stored in the controllers A1 to Ak.An example of the control handle management table is given in thefollowing Table 2. The control handle management table stores the clientindexes of the audio clients C1 to Cj and the controller indexes of thecontrollers A1 to Ak that have the controller handles for the audioclients C1 to Cj in association with each other. A control handlerepresents the authority to control an audio client. In the exampleshown in Table 2, the control handle for the audio client C1 is obtainedby the controller A1, but the control handles for the audio clients C2and Cj are not obtained by any of the controllers. TABLE 2 controlhandle management table controller having audio client control handle C1A1 C2 — . . . . . . Cj —

Now, the operation of the embodiment will be described with reference tothe flowchart in FIG. 76 particularly in connection with the contentserver S1, the audio client C1, and the controller A1. Note that in FIG.76, the steps of obtaining a music list (S30302 and S20102 in FIG. 73)that have been detailed in conjunction with the first embodiment are notshown.

The controller A1 obtains a control handle necessary for controlling theaudio client C1 before instructing the audio client C1 to reproduce amusic piece. More specifically, the controller A1 refers to a controlhandle management table and determines whether or not the control handlefor the audio client C1 is locked (S30311).

If the control handle for the audio client C1 has already been obtainedby any of the other controllers A2 to Ak, the controller index of thecontroller is recorded in connection with the client index of the audioclient C1 in the control handle management table shown in Table 2. Thestate in which the control handle has already been obtained is referredto as “the control handle is locked.” Meanwhile, if the control handlefor the audio client C1 is not obtained by any of the other controllersA2 to Ak, no controller index is entered in association with the clientindex of the audio client C1. The state in which the control handle hasnot been obtained is referred to as “the control handle is not locked(is unlocked).” In the control handle management table in Table 2, forexample, the control handle for the audio client C2 is not locked.

When the control handle for the audio client C1 is locked, thecontroller A1 cannot successfully obtain the control handle. Meanwhile,if the control handle is unlocked, the controller A1 requests thecontent server S1 to permit the controller A1 to obtain the controlhandle (S30312). In response to the request, the content server S1permits the controller A1 to obtain the control handle (S20111). In thisway, the controller A1 obtains the control handle and locks the controlhandle so that the other controllers A2 to Ak do not obtain the handle(S30313). More specifically, the controller A1 updates the controlhandle management table and stores the controller index of thecontroller A1 in association with the client index of the audio clientC1. The content server S1 updates the control handle management tablesin the other controllers A2 to Ak in synchronization with the aboveoperation.

The controller A1 that has obtained the control handle instructs theaudio client C1 to reproduce a music piece in a music list specified inresponse to the user's operation through the content server S1 (S30314).The content server S1 transfers the reproducing instruction to the audioclient C1 (S20112). The audio client C1 starts to reproduce the musicpiece specified in response to the reproducing instruction (S10211).

The audio client C1 finishes reproducing the music piece to the end andtransmits a completion status to the content server S1 as shown in FIG.77 (S10212). The content server S1 transfers the completion status toall the controllers A1 to Ak (S20113).

The controller A1 determines whether or not the completion status isfrom the audio client C1 whose control handle is obtained by thecontroller A1 (S30315). If it is the audio client whose control handleis obtained by the controller A1, the controller carries out continuousreproducing processing (S30316). If otherwise, the controller ignoresthe completion status and simply monitors the state of the audio clientC1. In this example, the controller A1 has the control handle for theaudio client C1, therefore carries out continuous reproducing processing(S30316) and instructs to reproduce the next music piece based on themusic list (S30314).

Meanwhile, if the audio client C1 does not reproduce the music piece tothe end, and stops reproducing midway, the audio client transmits a stopstatus to the content server S1 (S10213). The content server S1transmits the stop status to all the controllers A1 to Ak (S20114).

The controller A1 determines whether or not the stop status is from theaudio client C1 whose control handle is obtained by the controller A1(S30317). If the status is from the audio client whose control handle isobtained by the controller A1, the controller unlocks the control handlefor the audio client C1 (S30318). If otherwise, the controller ignoresthe stop status.

In addition to the above case in which the stop status is received fromthe audio client C1 whose control handle is obtained by the controllerA1, the controller A1 also unlocks the obtained control handle when itis disconnected from the content server S1. Once the control handle forthe audio client C1 is unlocked, the control handle can be obtained byany of the controllers A1 to Ak.

Note that when music pieces included in a music list are stored in aplurality of content servers S1 and Si, the audio client C1 switches theconnection between the content server S1 to the other content server Sias shown in FIG. 77 similarly to the above described first embodiment.If the content server Si receives the completion status from the audioclient C1, it is unknown which controller among the controllers A1 to Akhas instructed the audio client C1 to reproduce the music piece that theaudio client C1 has finished reproducing. Therefore, also in this case,the content server Si transfers the completion status to all thecontrollers A1 to Ak. Since the controllers A1 to Ak have the controlhandle management tables, they carry out continuous reproducingprocessing only when the completion status is from the audio clientwhose control handle is obtained by each of the controllers. In thisexample, the controller A1 has obtained the control handle for the audioclient C1, and therefore only the controller A1 carries out continuousreproducing processing.

As in the foregoing, the controllers A1 to Ak each have a control handlemanagement table, and therefore if the content server transmits thecompletion status transmitted from the audio client C1 to all thecontrollers A1 to Ak, the controllers A1 to Ak each carry out continuousreproducing processing only when the completion status is received froma corresponding audio client whose control handle is obtained by eachcontroller. Consequently, the possibility of competition betweencontinuous reproducing instructions can be eliminated, and continuousreproducing processing can normally be carried out.

Note that the control handle management tables are stored in thecontrollers A1 to Ak according to the embodiment, but they may be storedin the content servers S1 to Si.

Rather than locking the control handle, the control handle may beobtained by the controller that instructs last. More specifically, whena controller A1 obtains the control handle for an audio client C1, and adifferent controller A2 instructs the audio client C1 to reproduce, thecontroller A2 may obtain the control handle while the controller A1 maylose the control handle.

1.2.3.3.8. Continuous Reproducing Control by Content Server

To begin with, a simple example including a single content server, asingle audio client, and a single controller will be described inconjunction with FIG. 78.

Similarly to the above-described embodiment, the controller A1 instructsthe audio client C1 to reproduce a music piece through the contentserver S1. The audio client C1 responds to the instruction to requestthe content server S1 to provide the music content of the music piece.The content server S1 responds to the request to distribute the musiccontent to the audio client C1. The audio client C1 starts to reproducethe music piece based on the music content and transmits a completionstatus to the content server S1 once the audio client finishesreproducing the music piece to the end. The content server S1 respondsto the received completion status to instruct the audio client C1 tocontinuously reproduce the next music piece as opposed to the embodimentdescribed above and transmits a stop status to the controller A1.

The process will be detailed in conjunction with the flowchart in FIG.79. According to the embodiment, computer programs to carry out thesteps shown in FIG. 79 are installed in the content server S1, the audioclient C1, and the controller A1. Steps S30323, S10221, and S20123 toS21125 in FIG. 79 are different from the embodiment shown in FIG. 73,and therefore these steps will be particularly detailed in the followingdescription.

The controller A1 instructs the audio client C1 to reproduce a musicpiece similarly to the above described embodiment, but unlike the aboveembodiment, a list construction key used for obtaining a music list instep S30302 is transmitted to the audio client C1 (S30323).

The audio client C1 requests the content server S1 to provide the musiccontent of the music piece specified similarly to the first embodimentand transfers the list construction key transmitted from the controllerA1 to the content server S1 (S10221).

The content server S1 distributes the music content of the specifiedmusic piece to the audio client C1 similarly to the embodiment describedabove but produces a music list based on the list construction keytransferred from the audio client C1 (S20123), which is different fromthe above described embodiment. The list construction key and the musiclist are stored in association with the client index of the audio clientC1 as client information. In this way, the content server S1 is informedof the music list being reproduced by the audio client C1 in response toan instruction from the controller A1.

After the end of reproducing the music piece, the content server S1receives a completion status from the audio client C1 and transmits astop status to the controller A1 as opposed to the above describedembodiment (S20124). The content server S1 instructs the audio client C1to reproduce the next music piece based on the music list produced instep S20123 (S20125).

As in the foregoing, according to the embodiment, the content server S1itself instructs continuous reproducing, and therefore continuousreproducing processing can normally be carried out without competitionbetween continuous reproducing instructions from controllers.

In the above example, there is only one client, but there may be two ormore clients. In the example shown in FIG. 80, the audio clients C1 andC2 are connected to the content server S1. Similarly to step S20123described above, the content server S1 stores the list construction keyand the music list presently being reproduced by the audio client C1 toC2. When a completion status is transmitted to the content server S1from the audio client C1, the content server S1 instructs the audioclient C1 to carry out continuous reproducing based on the stored musiclist of the audio client C1 and transmits a stop status to thecontroller A1. When a completion status is transmitted to the contentserver S1 from the audio client C2, the content server S1 instructs theaudio client C2 to carry out continuous reproducing based on the musiclist of the audio client C2 and transmits a stop status to thecontroller A1. In this way, the content server S1 instructs continuousreproducing separately to the audio clients C1 and C2 and thereforethere is no possibility of competition between continuous reproducinginstructions.

Similarly to the audio clients, two or more content servers may beprovided. In the example shown in FIG. 81, the audio clients C1 and C2are connected to the content server S1, and the audio client C3 isconnected to the content server S2. In this case, one content server isconnected to each client, and the audio client transmits a completionstatus only to the content server that the client is connected to.Similarly to the above, in response the completion status received fromthe audio client C1, the content server Si instructs the audio client C1to carry out continuous reproducing. In response to a completion statusfrom the audio client C2, the content server S1 instructs the audioclient C2 to carry out continuous reproducing. Further in this case, inresponse to the completion status received from the audio client C3, thecontent server S2 instructs the audio client C3 to carry out continuousreproducing. In this case, only one content server instructs each audioclient to carry out continuous reproducing on the network, and thereforethere is no possibility of competition between continuous reproducinginstructions.

In the example shown in FIG. 81, when the controller A1 instructs theaudio client C2 to reproduce a music piece stored in the content serverS2 through the content server S1, the audio client C2 disconnects fromthe content server S1, and then connects to the content server S2 asshown in FIG. 82. At the time, the content server S2 produces a musiclist based on a list construction key transmitted from the audio clientC2 and stores the list construction key and the music list as the clientinformation of the audio client C2. When the audio client C2 finishesreproducing the music piece distributed from the content server S2, theaudio client C2 transmits a completion status to the content server S2.The content server S2 responds to the completion status to instruct theaudio client C2 to carry out continuous reproducing and transmits a stopstatus to the controller Al. Again, only one content server instructscontinuous reproducing to each audio client on the network, andtherefore there is no possibility of competition between continuousreproducing instructions.

Similarly to the audio clients and the content servers, two or morecontrollers may be provided. In the example shown in FIG. 83, there arethe controllers A1 and A2. The content server S1 transmits a stop statusnot only to the controller A1 but also to the controller A2 in responseto a completion status from the audio client C1 or C2. The contentserver S2 also transmits a stop status not only to the controller A1 butalso to the controller A2 in response to a completion status receivedfrom the audio client C3. In this way, the controllers A1 and A2 are notcapable of instructing continuous reproducing, can simply monitor thestates of the audio clients C1 to C3, and therefore do not affectcontinuous reproducing processing.

1.2.3.3.9. Continuous Reproducing Control by Audio Client Itself

According to the embodiment, computer programs to carry out the stepsshown in FIG. 84 are installed in the content servers S1 to Si, theaudio clients C1 to Cj, and the controllers A1 to Ak. Steps S10233 toS10235 in FIG. 84 are different from the embodiment shown in FIG. 79,and therefore these steps are particularly detailed here.

Similarly to the embodiment shown in FIG. 79, the controller A1instructs the audio client C1 to reproduce a specified music piece andtransmits a list construction key to the audio client C1 (S30323). Theaudio client C1 requests the content server S1 to provide the specifiedmusic piece and starts to reproduce the music piece distributed from thecontent server S1 in response to the request (S10202). At the time, theaudio client C1 stores the list construction key transmitted from thecontroller A1.

The audio client C1 transmits the stored list construction key to thecontent server S1 and requests the content server S1 to provide themusic list the same as that used in selecting the music piece by thecontroller A1 (S10233). The content server S1 produces a music listbased on the received list construction key and transmits the list tothe audio client C1 (S20133). The audio client C1 stores the receivedmusic list and specifies the music piece presently being reproduced inthe music list (S10234).

The audio client C1 finishes reproducing the music piece to the end andreproduces the next music piece based on the stored music list (S10235).

Note that when the music pieces included in the music list are stored ina plurality of content servers, the audio client C1 carries out serverswitching processing similarly to the above.

As in the foregoing, according to the embodiment, the audio client Clitself has a list construction key and obtains a music list using thekey, and therefore the audio client C1 itself can carry out thecontinuous reproducing processing. Therefore, the audio client C1 doesnot receive a continuous reproducing instruction from the controller A1or the content server S1, and there is no possibility of competitionbetween continuous reproducing instructions.

According to the embodiment, the audio client C1 obtains the music listusing the list construction key while the music piece is reproduced, itmay be obtained after reproducing the music piece. Although the audioclient C1 stores the obtained music list, the audio client may obtain amusic list using a list construction key every time continuousreproducing is carried out rather than storing the list.

1.2.3.3.10. Continuous Reproducing Control Using Reproducing InstructionManagement Table

According to the embodiment, computer programs to carry out the stepsshown in FIG. 85 are installed in the content servers S1 to Si, theaudio clients C1 to Cj, and the controllers A1 to Ak. Steps S30341 toS30345, and S20141 in FIG. 85 are different from the embodiment shown inFIG. 76, and therefore these steps are particularly detailed here.

The content server S1 according to the embodiment stores a reproducinginstruction management table including client indexes and controllerindexes in association with each other. An example of the table is shownin the following Table 3. The reproducing instruction management tableshown in Table 3 stores the controller index of the controller A1 thathas last instructed the audio client C1 to carry out reproducing. Thetable also stores the controller index of the controller A2 that haslast instructed the audio client C2 to carry out reproducing. TABLE 3reproducing instruction management table client controller C1 A1 C2 A2C3 — . . . . . . Cj —

Now, referring to the flowchart in FIG. 85, the operation of theembodiment will be described.

A certain controller instructs a certain audio client to reproduce amusic piece stored in a certain content server (S30341).

As shown in FIG. 86, the controller A1 instructs the audio client C1 toreproduce a music piece stored in the content server S1 through thecontent server S1. In this example, the audio clients C1 and C2 andcontrollers A1 to A3 are connected to the content server S1.

The controller A1 determines whether or not the audio client C1 isconnected to the content server S1 (S30342). In this example, the audioclient C1 is connected to the content server S1, and the processproceeds to step S30314.

The controller A1 instructs the audio client C1 to reproduce a musicpiece specified in a music list through the content server S1 (S30314).The content server S1 carries out predetermined reproducing instructionmanagement processing in response to the reproducing instruction(S20141).

More specifically, referring to FIG. 87, the content server S1 storesthe controller index of the controller A1 in association with the clientindex of the audio client C1 in the reproducing instruction managementtable (S201441). In this way, the content server S1 stores thecontroller A1 as the controller that has last instructed the audioclient C1 to carry out reproducing. The content server S1 transfers thereproducing instruction from the controller A1 to the audio client C1(S201412).

The audio client C1 starts to reproduce a music piece in response to thereproducing instruction from the controller A1 (S10211) and transmits acompletion status to the content server S1 once the reproducing iscomplete (S10212).

The content server S1 specifies the controller A1 that has lastinstructed the audio client C1 to carry out reproducing by referring tothe reproducing instruction management table in response to thecompletion status from the audio client C1 and transmits the completionstatus to the controller A1 and a stop status to the other controllersA2 and A3 (S201413). In response to the received completion status, thecontroller A1 carries out continuous reproducing processing to the audioclient C1 (S30316). Meanwhile, in response to the received stop status,the controllers A2 and A3 do not take any positive action and simplymonitor the state of the audio client C1.

When the audio client C1 reproduces a music piece in response to theinstruction from the controller A1, and any other controller such as thecontroller A2 instructs the audio client C1 to reproduce another musicpiece, the audio client C1 stops reproducing the present music piece andstarts to reproduce the new music piece in response to the instructionfrom the controller A2. At the time, the content server S1 updates thereproducing instruction management table and replaces the controllerindex of the controller A1 by the controller index of the controller A2as shown in Table 4. TABLE 4 reproducing instruction management tableclient controller C1 A1→A2 C2 A2 C3 — . . . . . . Cj —

Now, as shown in FIG. 88, how the controller A3 instructs the audioclient C1 to reproduce a music piece stored in the different contentserver S2 through the content server S1 will be described.

The controller A3 determines whether or not the audio client C1 isconnected to the content server S2 (S30342). In this example, since theaudio client C1 is not connected to the content server S2, thecontroller A3 carries out predetermined server switching processing(S30343).

More specifically, referring to FIG. 89, the controller A3 instructs theaudio client C1 to switch from the content server Si to the contentserver S2 through the content server S1 (S303431). The content server S1transmits the switching instruction to the audio client C1 (S201401).The audio client C1 disconnects the content server S1 presently beingconnected (S102401) and requests connection to the new content server S2in response to the switching instruction (S102402). The content serverS2 establishes connection with the audio client C1 in response to therequest (S201402). The controller A3 checks the connection with thecontent server S2 (S30344).

Then, the controller A3 instructs the audio client C1 to reproduce amusic piece through the content server S2 (S30314). The content serverS2 responds to the reproducing instruction to store the controller indexof the controller A3 in association with the client index of the audioclient C1 in the reproducing instruction management table as in Table 5(S201441). TABLE 5 reproducing instruction management table clientcontroller C1 A3 C2 — C3 — . . . . . . Cj —

The content server S2 transfers the reproducing instruction from thecontroller A3 to the audio client C1 (S201412).

The audio client C1 starts to reproduce the music piece in response tothe reproducing instruction from the controller A3 (S10211), andtransmits a completion status to the content server S2 after reproducingthe music piece (S10212). The content server S2 specifies the controllerA3 that has last instructed the audio client C1 to reproduce byreferring to the reproducing instruction management table in response tothe completion status received from the audio client C1. Then, thecontent server S2 transmits a completion status to the controller A3 anda stop status to the other controllers A1 and A2 (S1413). The controllerA3 carries out continuous reproducing processing to the audio client C1in response to the received completion status (S30316). Meanwhile, thecontrollers A1 and A2 do not take any positive action in response to thestop status and simply monitor the state of the audio client C1.

As in the foregoing, according to the embodiment, the content servermanages the controller that has last instructed the audio client tocarry out reproducing and transfers a completion status from the audioclient only to the controller, and therefore only the controllerinstructs the audio client to carry out continuous reproducing.Consequently, there is no possibility of competition between continuousreproducing instructions, and the continuous reproducing processing cannormally be carried out.

1.2.4. AV Receiver Control

As shown in FIG. 90, AVR clients AC1 and AC2 are connected to the LAN12. The AV receiver AVR1 is connected to the AVR client AC1 by EIA-232.The AV receiver AVR2 is connected to the AVR client AC1 through USB. TheAV receiver AVR3 is connected to the AVR client AC2 through amanufacturer-specific serial interface.

The AVR clients AC1 and AC2 may each notify information related to theinterface such as the EIA-232 and USB to the content server Si when theconnection with the content server is established.

For the USB, the AVR client AC1 can obtain machine information such asthe vendor ID or product ID of the AV receiver AVR2 and notify theinformation to the content server Si. For the EIA-232, the AVR clientAC1 usually cannot obtain the machine information of the AV receiverAVR1, and therefore the vendor ID or product ID of the AV receiver AVR1are registered in the AVR client AC1 in advance, so that the AVR clientcan notify the information to the content server Si.

When there are a number of AV receivers that can be connected, thecommunication protocol with the AVR client is predetermined, so that theAVR client may obtain the machine information of the AV receiver. Forexample, the AVR client may transmit a packet for inquiring aboutmachine information at prescribed intervals (such as one second) inprescribed communication conditions (including the bit rate, bit length,and parity), and the AV receiver may return a packet including themachine information in response. In this way, the AVR client can specifythe connected AV receiver. In this case as well as the case with theUSB, the AVR client may obtain the machine information of the AVreceiver after the connection with the content server is established,and therefore, a change in the machine information is notified to thecontent server Si when the machine information of the AV receiver isobtained.

Consequently, the content server Si may obtain the machine informationof all the AV receivers AVR1 to AVR3 connected to or to be connected tothe AVR clients AC1 and AC2. The machine information is also notified tothe controller Ak from the content server Si, and therefore thecontroller Ak can obtain the machine information.

As shown in FIG. 91, the AV receiver AVR has various controlled elementssuch as a volume control, an input selector switch, and a DSP (digitalsignal processor) for sound field control. The controller Ak specifiessuch a controlled element and issues a control command. Therefore, thecontroller has the machine information about the kinds of controlledelements the AV receiver AVR has.

Note that since the content server Si has the machine information, thecontroller Ak may request the content server Si to provide the machineinformation using the vendor ID and product ID of the AV receiver AVR asa key.

The control command is output from the controller Ak and transmitted tothe AV receiver AVR through the content server Si and the AVR client AC.Conversely, the status is output from the AV receiver AVR andtransmitted to the controller Ak through the AVR client AC and thecontent server Si.

The AVR client AC determines that the control command is for the AVreceiver AVR and then outputs the control command to the AV receiverAVR. If the command is used to control the value of the volume, thecontrol command issued by the controller Ak is transmitted to the AVreceiver ACR through the content server Si and the AVR client AC, sothat the volume is controlled.

Referring to FIG. 92, the controller Ak transmits the control command tothe content server Si (S35), the content server Si transmits the commandto a specified AVR client AC (S28), and then the AVR client transmits itto the AV receiver AVR (S101). The AVR client AC transmits the statusreceived from the AV receiver AVR to the content server Si (S102), thecontent server Si transmits this to the controller Ak (S29), and thecontroller Ak updates the status of the AV receiver AVR in response(S36).

As shown in FIG. 93, the content server Si, the AVR clients AC1 to AC3,and the AV receivers AVR 11, AVR12, AVR21, AVR31, and AVR32 transmit acontrol command in a tree-like path having the content server Si as theroot.

Referring to FIG. 94, the controller Ak determines an AV receiver AVR tobe controlled and the control content (S3501) and produces the main bodyof a command based on the control content (S3502). As shown in FIG. 95A,the controller Ak then transmits the control command including thecommand main body and the attached destination information to thecontent server Si (S3503). The destination information in this exampleincludes an AV receiver specifying portion that specifies the AVreceiver AVR to be controlled and an AVR client specifying portion thatspecifies the AVR client AC connected to the AV receiver AVR.

The content server Si receives the control command and extracts the AVRclient specifying portion from the received command as shown in FIG. 95B(S2801). The content server Si determines the specified AVR client ACbased on the AVR client specifying portion. The content server Si thentransmits the control command removed of the AVR client specifyingportion to the specified AVR client AC (S2802).

The AVR client AC receives the control command and extracts the AVreceiver specifying portion from the received command as shown in FIG.95C (S1011). The AVR client AC determines the specified AV receiverbased on the AV receiver specifying portion. The AVR client AC thentransmits the control command made up only of the command main body tothe specified AV receiver (S2802).

In this way, the control command removed of unnecessary portions issequentially transferred, so that the network traffic can be alleviated.Note however that the control command may be transferred as it iswithout being removed of the specifying portions.

In each of the stages, the character string of the command main bodydoes not have to be entirely the same as long as it has the samemeaning. More specifically, the control command eventually transmittedto the AV receiver AVR from the AVR client AC needs only be comprehendedby the AV receiver AVR.

In this way, the AV receiver AVR controls the controlled element basedon the received control command. Consequently, in response to a changein the status of the controlled element, the AV receiver AVR transmitsthe status to the AVR client AC. The status is made only of the statusmain body as shown in FIG. 96A.

The AV client AC receives the status of the AV receiver AVR and storesit (S1021), adds the source information to the received status andtransmits the resultant status to the content server Si as shown in FIG.96B (S1022). The source information in this example includes the AVreceiver specifying portion that specifies the AV receiver AVR that hastransmitted the status.

The content server Si receives the status from the AVR client AC, addsan AVR client specifying portion to the received status as shown in FIG.96C, and then transmits the resultant status to the controller Ak(S2901).

The controller Ak receives the status from the content server Si,extracts the AVR client specifying portion and the AV receiverspecifying portion from the status and updates the status of the AVreceiver AVR (S3601).

Note that there are not only the statuses of the controlled elements butalso the statuses of elements that cannot be controlled by thecontroller Ak (such as the level information of a sound signal). Thesestatuses are also transmitted to the controller Ak through the AVRclient AC and the content server Si. The status is transmitted not onlywhen the controlled element of the AV receiver AVR is controlled basedon the control command, but also when the status changes. Morespecifically, when the connection between the AVR client AC and the AVreceiver AVR is confirmed, the AVR client AC obtains the status of theAV receiver AVR and transmits the status to the content server Si.

In this way, the controller Ak that eventually receives the status canbe informed of the status of each of the AV receivers AVR. Thecontroller thus checks the control and displays the status.

Note statuses for the purpose of display that could frequently changemay be transmitted less frequently by the AV receiver AVR or the AVRclient AC. The frequently changing statuses can hardly be recognized ifthey are displayed as they change, and the high transmitting frequencyof these statuses can cause unwanted traffic increase, which alsoincreases the load on the content server.

A controlled element in a complicated structure may have a plurality ofcontrolled portions. For example as shown in FIG. 91, the DSP forcontrolling the sound field necessitates many kinds of coefficient datato be set, and the settings are made by a microcontroller that controlsthe DSP. The settings are changed by the key operation by the user asthe status state is displayed by the AV receiver main body or a displayconnected thereto in a stand-alone system. The operation is carried outby the firmware of the micro controller. In order to achieve complicatedsettings and make the operation easier, the program capacity must beincreased or a high performance display is necessary. This could affectthe product price or development cost.

In this system, a number of setting patterns of coefficient data areprovided to the content server Si, so that one of the patterns may beselected from a hierarchy menu displayed at the controller Ak and thecoefficient data may be set through the AVR client AC accordingly.

Since a plurality of AV receivers AVR may be under the control of thecontroller Ak, time setting for the AV receivers AVR or the like can becarried out at a time. In addition, by monitoring the statuses of theseAV receivers AVR, cooperative operation such as relay recording can becarried out.

Now, the case when the volume of an AV receiver AVR connected to an AVRclient AC is raised will be described.

Referring to FIG. 97, the controller Ak checks the connection with theclient (S3011) and determines whether the client is an AVR client AC ifthe connection is established (S3014). If the client is an AVR clientAC, a control command for raising the volume is transmitted to thecontent server Si (S35). The content server Si transmits this command tothe AVR client AC (S28), and the AVR client AC transmits the command tothe AV receiver AVR (S110). The AVR client AC receives the statusindicating that the volume has been raised and transmits the status tothe content server Si (S102). The content server Si transmits thecommand to the controller Ak (S29), and the controller Ak updates thestatus of the AV receiver AVR in response and resumes monitoringoperation as shown in FIG. 34 (S36).

Now, the operation of the AVR client AC to transfer the status of the AVreceiver AVR to the content server will be described in conjunction withFIG. 98.

The AVR client AC receives packet data from the AV receiver AVR (S1021)and determines whether the data is volume information (S1022). If thedata from the AV receiver AVR is by EIA-232, the packet receiving isperformed by serial receiving interruption, and the data is placed in aqueue. The queue is read out at prescribed intervals and subsequentprocessing is carried out.

Then, if the received data is volume information, the AVR client ACstores the volume value (S1023). It is determined whether or not thedata is the volume information (S1022) and the volume information isstored (S1023) before the data is placed in the queue. Meanwhile, if thereceived data is not volume information, the AVR client AC adds an AVreceiver specifying portion that indicates that the status is from theAV receiver AVR to the packet data and transmits the resultant data tothe content server Si (S1024).

After the volume value is stored, it is determined whether or not thevolume information is received for the first time (S1025). If it isreceived for the first time, the AVR client AC proceeds to step S1028,but otherwise the AVR client AC determines whether 200 milliseconds ormore has passed after the volume value is transmitted to the contentserver (S1026). If 200 milliseconds or more has passed, the AVR clientAC compares the volume value previously transmitted and the storedvolume (S1027). If they are different, the AVR client AC adds an AVreceiver specifying portion indicating that the status is from the AVreceiver AVR to the volume information and transmits the resultantstatus to the content server Si (S1028).

The status of the volume value comes in at shorter intervals than theother statuses and therefore could increase the load upon the contentserver Si and the controller Ak or unwanted traffic on the network. Thevolume information is simply used for display at the controller Ak andtherefore needs only to be transmitted at intervals enough for display.Therefore, when the volume information is received, only the valuethereof is stored, and the information is transmitted to the contentserver Si at appropriate intervals (200 milliseconds in this example)only when there is a change in the value.

Now, the operation of the AVR client AC to transfer a command from thecontent server Si to the AV receiver AVR will be described inconjunction with FIG. 99.

The AVR client AC receives a control packet for the AV receiver AVR(S1031) and extracts the control command for the AV receiver AVR fromthe packet (S1032). The AVR client AC determines whether or not thecontrol command is a command to inquire about the volume value (S1033).If the command is a volume value inquiry command, the AVR client ACproduces volume information based on the stored volume value (or asuitable initial value if there is no received value) (S1034), adds anAV receiver specifying portion indicating a status from the AV receiverAVR to the volume information and transmits the result to the contentserver Si (S1035).

Meanwhile, if the command is not a volume value inquiry command, thecontrol command for the AV receiver AVR is transmitted to the AVreceiver AVR (S1036). If the interface between the AVR client AC and theAV receiver AVR is by EIA-232, the transmission from the AVR client ACto the AC receiver AVR is carried out by interruption on a byte-basis.The control command from the content server Si is once stored in aqueue. The queue is read out by interruption at prescribed intervals orbuffer empty interruption in serial transmission and transmitted on abyte-basis.

According to the embodiment, the volume information is transmitted tothe content server Si only when there is a change except for the firsttime. Therefore, if the AV receiver AVR responds to the volume valueinquiry command from the content server Si to return the volume valueand there is no change in the volume value, the AVR client AC does notreturn the volume value to the content server Si. To cope with this, theAVR client AC responds to the volume value inquiry command from thecontent server Si not through the AV receiver AVR. In the embodiment,when the power supply for the AV receiver AVR is turned on, the initialvolume value is always transmitted to the AVR client AC as a status.However, the AVR client AC could not receive the initial value in somecases depending upon the timing of turning on the power supply.

Therefore, as shown in FIG. 100, the AVR client AC preferably respondsonly for the first time through the AV receiver AVR. More specifically,if the control command from the content server Si is a volume valueinquiry command, the AVR client AC determines whether the volume valuehas not been received yet (S1034). If the value is not received, theprocess proceeds to step S1036, and if the value has already beenreceived, the process proceeds to step S1034.

Note that if there are a plurality of kinds of AV receivers and thecontroller Ak controls these AV receivers, the controller Ak may issue adedicated control command depending on the kinds of the AV receivers.Alternatively, the controller may issue a general-purpose controlcommand regardless of the kind of the AV receivers, and the contentserver may change the general-purpose command to the dedicated command.

1.2.5. Firmware Updating

The content server as will be described can update firmware installed ina client. Here, a client requests the content server to update it, thecontent server inquires the client and then updates it, or the contentserver forcibly updates it.

Now, how the client requests the content server to update will bedescribed. Referring to FIG. 101, the client requests the content serverto provide firmware information (S103), the content server responds tothe request to return firmware information to the client (S201), and theclient receives the information (S103). The client then specifies thefirmware (S104), and the content server responds to this to prepare fortransferring the firmware (S202). The client then requests the contentserver to provide the firmware (S105), the content server responds tothe request to transfer the firmware to the client (S203), and theclient receives the firmware (S105). The client then updates thefirmware (S106) and transmits an end status when the updating is over(S107), and the content server receives the status (S204).

How the firmware will be updated will be detailed in conjunction withFIG. 102. When the updating is started by the content server, theprocess starts from step S2012. When the updating is started by theclient, the process starts from step S1033.

The content server reads the file of firmware information and produces afirmware information database shown in FIG. 15 (S2011). For example, thecontent server reads a necessary file for updating on a client-basis andproduces an update information file. Therefore, the version of thefirmware can be determined based on the information file. The clienttransmits the product ID and the firmware ID to the content server whenit is activated (S1031).

When the updating is started by the content server, such as when thecontent server determines the firmware is old based on the product IDand firmware ID of the client, or when the content server obtains newfirmware from a site on the Internet, the content server issues afirmware updating request command to request the client to update thefirmware and provides information related to the new firmwarerecommended for updating if necessary (S2012). If the user does not wishto update the recommended firmware, the client refuses the updatingrequest from the content server, and the process immediately ends(S1032). When the user defers the determination as to whether or not toupdate the recommended firmware, the process immediately ends (S1032).In the latter case, however, the client instructs the content server torequest updating again after a prescribed time period. If the useraccepts the recommended firmware updating, the client continues theprocessing (S1032). In this case, if the content server presentsspecific firmware to the client, the client proceeds to step S1035, andimmediately starts updating the firmware. If the content server does notpresent any specific firmware and simply requests updating, the clientproceeds to step S1033 and obtains a firmware list.

Note that the firmware updating request command may be issued by thecontroller as a server request. In this case, the controller obtains afirmware list related to the client controlled and monitored by thecontroller from the content server similarly to steps S1033 and S1034and selects firmware desired by the user. Information on the firmwareselected by the controller is presented to the client as firmwareinformation recommended for updating.

If the updating request is accepted or the client starts updating, theclient requests the content server to provide the firmware list (S1033).The firmware list includes firmware pieces applicable to specificclients. The content server does not always have such a firmware listbut produces the list every time a client requests for such a list. Thefirmware list is produced basically in the same way as the way ofproducing the music list described above. Note however that when afirmware list is produced, the content server uses the firmwareinformation database as shown in FIG. 15. The database stores firmwareinformation for several firmware pieces. Now the method of producing thefirmware list will be detailed.

Referring to FIG. 103, the content server initializes the indexrepresenting the number of firmware information stored in the firmwareinformation database to zero (S20131).

The content server then determines whether the product ID of thefirmware information indicated by the index matches the product ID ofthe client (S20132). If they match, the content server adds the firmwareinformation to the firmware list (S20133) and then increases the index(S20134). Meanwhile, if they do not match, the content server skips stepS20133 and immediately increases the index (S20134).

The content server then determines whether the firmware informationnumber represented by the index is smaller than the number n of all thefirmware information pieces (S20135). If the number is smaller than n,the process returns to step S20132, while if the number is not less thann, the process of producing the firmware list ends.

By the above processing, the content server picks up firmwareinformation having a matching product ID in the firmware informationdatabase and produces a firmware list. In this way, the firmware listsare not formed into a database in advance, but a list is produced everytime a client requests for one, and therefore the memory region forconstantly storing firmware lists is not necessary.

The content server then returns the produced firmware list to the sourceclient (S2013). The firmware list is divided for transmission from thecontent server to the client similarly to the music list describedabove.

More specifically, referring to FIG. 104, the client transmits afirmware list request command including the product ID of the client, anobtaining start index representing the first firmware information to beobtained, and an obtaining number that represents the number of firmwareinformation pieces to be obtained to the content server (S1033). Thecontent server responds to the firmware list request command to extractfirmware information whose product ID is the same as the product ID ofthe client and returns firmware information pieces as many as theobtaining number in the firmware information represented by theobtaining start index to the client (S2031). At the time, the contentserver transmits an effective number representing the number of thefirmware pieces to be transmitted and the remaining number representingthe number of firmware pieces left out of the firmware list returned bythe content server to the client. The client receives a part of thefirmware list and stores it in the memory (S10331). The above describedprocessing is repeated until all the firmware lists are transmitted fromthe content server to the client.

Then, the client continues the processing if there is firmware the userdesires to download in the returned firmware list (such as an up-to-dateversion of firmware), and if there is none, the processing is stopped(S1034).

The content server transmits the firmware information of all theversions, either new or old, and therefore the client can change thefirmware to older version firmware because of malfunction and the like.

In the updating, the client notifies the status that indicates thetransition to the updating section to the content server (S1035). Thecontent server returns an error code indicating the presence/absence ofan error in response to the status (S2014). The client specifies thefile of the firmware to be downloaded (S1036). More specifically, theclient specifies a full path name stored in the obtained firmwareinformation list. The content server reads a specified file and storesthe file in the buffer (S2015).

The client then specifies the obtaining start address and data size(byte number) and obtains the data of the firmware (S1037). The contentserver reads out data for the specified byte number from the specifiedobtaining start address and transmits the data to the client (S2016).

The client determines whether or not the data of the firmware up to thelast piece has been obtained (S1038), and if the data has not thoroughlybeen obtained, the client returns to step S1037 and repeats the processof obtaining data. After the client finishes obtaining the data, theclient rewrites the firmware (S1039) and finishes updating (S1040). Thecontent server closes the opened file of the firmware and releases thebuffer (S2017).

When the client has finished rewriting the firmware, an unknown statusis transmitted to the content server. The client interrupts theconnection with the content server to reset (or activates the updatedfirmware) and notifies the client information to the content server.When the client fails to obtain the firmware data, a failure status maybe transmitted. The failure status may be used for re-transmitting thefirmware data.

Note that when the updating request is issued from the content server,the processing may be as follows. More specifically, in FIG. 102, thecontent server never fails to present firmware information to the clientat the time of updating request (S2012). When the firmware recommendedby the content server is to be updated, the process proceeds to stepS1035, while when the user selects desired firmware from the firmwarelist rather than updating the firmware recommended by the contentserver, the process proceeds to S1033.

As in the foregoing, the data of the firmware is transmitted to theaudio client through the LAN from the content server, so that thefirmware of the client can be updated for a short period, and thefirmware of a plurality of clients can be updated at a time. Since theproduct ID is used, firmware suitable for the client can automaticallybe selected for updating. Since the firmware ID is used, the firmware ofthe up-to-date version can automatically be selected for updating.

2. Other Embodiments

2.1. Audio Client Stored in Outlet BOX

An audio client may be stored in an outlet box 50 as shown in FIGS. 105and 106. The outlet box 50 generally includes a front panel 54 attachedto a wall 52, and a box member 56 attached to the back surface of thefront panel 54. According to the embodiment, a circuit for the audioclient as shown in FIG. 3 is provided in the box member 56. The LANcable is connected to the circuit for the audio client. The front panel54 is provided with a power supply receptacle 58, a power supply switch60, a modular jack (not shown), and a TV antenna terminal (not shown) aswell as an audio output terminal 62 for outputting an audio signal fromthe audio client. The audio client terminal 62 is connected to the rightand left speaker devices.

The audio client typically includes a display for displaying a musiclist and switches to select a desired music piece in the displayed musiclist. The display or switches are necessary for monitoring andcontrolling an audio client, and the use of a controller connected tothe same LAN 12 as the audio client permits the audio client to beremoved of the display or switches. In place of the controller, aportable remote controller connected by radio to the LAN 12 the same asthe audio client may be used.

In this way, the audio client is simplified and may be stored in theoutlet box 50 for home use. The simplified audio client stored in theoutlet box can only extract music or video from a network and reproduceit and cannot display or control.

As the Internet use comes to increase, particularly the infrastructurefor the broadband (high speed and large capacity) technique comes to bemore developed, there will be connection requests from a number of PCsper household to the Internet. The most typical way of connecting anumber of PCs at home is to build a LAN in the house, and morehouseholds will undoubtedly build their own in-home LANs before long.The use of the LAN allows music or video to be distributed to variousplaces in the house with only a single cable. The single cable cantransmit music/video signals as well as control signals, and thereforespecial knowledge about audio/video is not necessary in providing thesystem. In addition, the system is much advantageous in terms of thecost, and the system can spread not only for business use but also forhome use.

More houses to be newly built or reformed for general households areprovided with in-home LANs in consideration of easier Internetconnection, and it is a common practice to provide a LAN connector in anoutlet box 50. Therefore, when such a LAN is provided, a plurality ofaudio clients can easily be provided as well. More specifically, anaudio client can be built simply by connecting a speaker (includingpowered one). A video client can be built simply by connecting a videomonitor such as a TV. Therefore, the audio clients that would match thehouse interior in appearance can be set. In terms of productdevelopment, eye-catching, luxurious designs for the products are notnecessary, and the products can be designed by a simple designing methodthat puts more emphasis on functions. This can reduce the developmentcost. The simple structure alleviates recycling process, which is alsobeneficial.

In-home LAN distribution does not need a content medium such as a CD anda tape unlike conventional audio/vide equipment. More specifically, oncea content is stored in a content server, the media does not have to bemanaged. In the server-client arrangement through the in-home network,an audio client does not need any mechanical devices such as a mechanismfor inserting a media or a rotation driving device. Therefore, the sizeof the device can be reduced, and the product may have high reliabilityand prolonged useful life.

2.2. Obtaining Music Data on Internet

According to the above described embodiment, the audio client searchesfor a content server by broadcasting when it is turned on. However, whenthe power supply for all the content servers on the LAN 12 are off, nocontent server responds, and therefore the audio client must endlesslycontinue to search for a content server. In order to avoid it, the audioclient may be subjected to processing such as time-out error, but if thetime-out error is caused, the audio client cannot operate at all forexample for reproducing music.

In order to solve these disadvantages, when the audio client repeatsbroadcasting a prescribed number of times and still cannot find acontent server, the audio client may access and connect with a WWW(World Wide Web) server on the Internet.

In this case, as shown in FIG. 107, the LAN 12 is connected to theInternet 52 through a gateway 50. The WWW server 54 on the Internet 52has registered lists of music pieces provided at a music distributionsite 56. The lists include music piece information such as titles andartists' names and URLs (Uniform Resource Locator) where music data isprovided.

As shown in FIG. 108, when the server list is empty, the audio clientdetermines whether or not the number of retrial attempts in broadcastinghas reached a prescribed number such as three before returning to stepS1102 and trying to broadcast again (S1109). If the number of retrialattempts has not reached three, the audio client increases the number ofretrial attempts (S1110) and then returns to step S1102 to broadcastagain. Meanwhile, if the number of retrial attempts has reached three,the audio client connects by HTTP to the WWW server 54 on the Internet52 (S1111). If the audio client successfully connects, the searchingprocess ends (S1112), but if the audio client does not successfullyconnect before time-out, an error is caused (S1113).

When the audio client accesses the WWW server 52, it receives musicinformation or a URL from the server. The audio client analyzes thereceived information or URL and receives music data from the musicdistribution site 56 at the URL.

As in the foregoing, when there in no content server on the LAN 12 or acontent server present on the LAN does not operate, the audio clientautomatically accesses the site 56 on the Internet 52 to obtain musicdata. The client therefore does not have to endlessly search for acontent server on the LAN 12.

In the above example, when the number of retrial attempts reaches aprescribed number, the audio client connects to the WWW server 54 on theInternet 52. Alternatively, the audio client may access the WWW server54 on the Internet 52 if the client broadcasts a magic word and there isno response from any of the content servers on the LAN 12 after aprescribed time period.

2.3. Reproducing with Function of Changing Obtained Data Length

In the above embodiment, when the audio client Cj requests the contentserver Si to transfer music data, it always requests for a predeterminedamount of the music data. Therefore, there is no problem while thenumber of audio clients Cj to request the content server Si to transfermusic data is small, but as the number increases, the load imposed onthe content server Si increases, which prolongs the time between therequest by the audio client Cj to the content server Si for music piecedata transfer and actual transfer of the music piece data. Therefore, inorder to average the load on the content server Si, the amount of themusic piece data requested by the audio client Cj by a single requestcan be changed as required.

Now, an example of how to change the amount of music piece datarequested by the audio client Cj at a time depending on the time betweenthe request by the audio client Cj to the content server Si for musicpiece data transfer and actual transfer of the music piece data will bedescribed.

Referring to FIG. 109, the audio client Cj transmits a music piece datatransfer command that requests the content server Si to transfer musicpiece data (S1601) and operates a timer at the same time, so that theresponse time until the music data is transferred from the contentserver Si starts to be counted (S16011). Note that when the audio clientCj issues the music piece data transfer command for the first time, anappropriate amount of music data to be requested by a single request isunknown, and therefore the obtaining data length is predetermined.

Then, when the audio client Cj starts to receive the music piece data(S16012), it stops the timer and obtains the response time for the musicpiece data by the content server Si (S16013).

The audio client Cj refers to a comparison table shown in FIG. 110 anddetermines the obtaining data length corresponding to the obtainedresponse time (S16021). The comparison table has prescribed responsetime periods and prescribed obtaining data lengths in association witheach other. Since the longer the response time is, the greater the loadon the content server Si is, the obtaining data length is shorter forlonger response time. If for example the audio client Cj obtains aresponse time period of 20 msec, the obtaining data length is determinedas 8 Kbytes.

The audio client Cj again requests the content server Si to transfermusic data, while the obtaining data length determined as describedabove is transmitted (S1605). Then, the operation the same as the aboveis repeated (S16051 to S16061).

According to the embodiment, the obtaining data length of music piecedata that the audio client Cj requests the content server Si to provideis shorter as the response time is longer. Therefore, if the number ofaudio clients Cj that request the content server Si to transfer musicpiece data increases, the amount of music piece data to be transferredto each audio client Cj by a single request is reduced. Consequently,the load on the content server Si per audio client Cj is averaged, andthe content server Si can smoothly transfer music piece data to theplurality of audio clients Cj.

In the above example, the obtaining data length is determined dependingupon the response time from the content server. Alternatively, theobtaining data length may be determined depending on the data format ofthe music piece to be obtained. More specifically, in FIG. 35, before amusic piece data transfer request (S1601), the audio format of the musicpiece is obtained based on search data shown in FIG. 32. Then, based onthe audio format of the music piece, the obtaining data length is set.In general, MP3 format data is compressed and has a small size, whileWAV format data has a large size. Therefore, if the music data to beobtained is in the MP3 format, 4 Kbyte data for example may be obtainedby a single request, and for the WAVE format data, 16 Kbyte data may beobtained by a single request.

2.4. Skip Reproducing

In the above embodiment, the audio client Cj requests the content serverSi to transfer music piece data in the order in the music list. However,the user might sometimes wish to listen a music piece being presentlyreproduced all over from the start. The user might want to skip thepresently reproduced piece and listen to another piece in other cases.Therefore, the audio client Cj may be able to request music piece datatransfer in response to such a request from the user.

Referring to FIG. 111, while the audio client Cj reproduces a musicpiece 3 in a music list shown in FIG. 112, the audio client requests thecontent server Si to transfer music data in a specified range of themusic data of the music piece 3 (S1607), and the content server Siresponds to the request to return the music data in the specified rangeto the audio client Cj (S2604). The audio client Cj receives the dataand stores it in the memory 32 (S1608). The operation is repeated andthe music piece 3 is reproduced accordingly.

When the user tries to end reproducing the music piece 3 and listens toa music piece 4 while the music piece 3 is reproduced (case (1) in FIG.112), the user requests the audio client Cj to skip from the presentlyreproduced music to the music piece 4. The audio client Cj checks thecontent of the music list stored in the memory 32 in response to theskip request from the user and obtains the file name of the music piece4 (S1641). If there is no such skip request from the user, the processreturns to step S1607 and transfer of the data of the music piece 3 isrequested.

The operation of the audio client Cj and the content server Sithereafter is the same as the operation described in conjunction withFIG. 35 and therefore will not be described.

By the above described operation, the audio client Cj can carry out skipreproducing to the music piece 4 while the music piece 3 is reproduced.

Note that while the audio client Cj reproduces the music piece 3, theaudio client Cj can carry out skip reproducing by the same operation, ifthe user tries to listen to the music piece 3 all over again from thestart (case (2) in FIG. 112), if the user tries to listen to a musicpiece 5 (case (3) in FIG. 112), or if the user tries to listen to amusic piece 2 (case (4) in FIG. 112).

As in the foregoing, according to the embodiment, the use of the musiclist stored in the memory allows the audio client Cj to carry out skipreproducing from a music piece presently being reproduced to anothermusic piece.

2.5. Repeating Reproducing

Data can repeatedly be reproduced between first and second addressesspecified by the user, in other words, A-B repeating reproducing can beperformed. The user carries out the first A-B repeating operation andspecifies the first address indicating the start of repeating. Morespecifically, referring to FIG. 113, when the audio client requestsmusic piece data to be transferred (and obtained)(S1601), and there isthe user's operation (S1642), which is an A-B repeating request (S1643)by the first request (S1644), the audio client stores the addressspecified by the user as the first address (addr1). The obtaining datalength (size) is added to the previous obtaining start address (addr) toproduce an obtaining start address (addr)(S1646), and the processreturns to step S1601.

Then, the user carries out the second A-B repeating operation, specifiesthe second address that indicates the end of repeating, and startsrepeating operation. More specifically, in step S1644, since the A-Brepeating request is for the second time (not for the first time), theaddress specified by the user is stored as the second address (addr2)(S1647).

The audio client enters an A-B repeating mode (S1648). Morespecifically, the obtaining start address is changed to the firstaddress (S1649), and the audio client requests music piece data to betransferred (and obtained) (S1601). Here, the audio client determinesthat the A-B region is in a repeating state (S1650) and then determineswhether the obtaining start address (=the previous start address+theobtaining data length) is greater than the second address (S1651). Ifthe obtaining start address is still not more than the second address,the music piece data transfer request is continued (S1646 and S1601). Ifthe obtaining start address is greater than the second address in stepS1651, the obtaining start address is again changed to the first address(S1652), and a music piece data transfer request is carried out (S1601).In this way, the repeating reproducing can be performed between thefirst and second addresses. The user can release the repeating state byrepeating releasing operation (S1643, S1653, and S1654).

2.6. Midway Reproducing

The user can specify an obtaining start address (for example byinputting start time) in order to reproduce a music piece from thespecified address. More specifically, referring to FIG. 114, when theaudio client requests music piece data to be transferred (andobtained)(S1601), and there is the user's operation (S1656), whichspecifies an address (S1657), the audio client obtains the addressspecified by the user (S1658). The address is produced from the totalreproducing time of the music piece and the start time input by theuser. The obtaining start address is changed to the address specified bythe user (S1659), and the transfer of the music piece data is requested(and the music piece data is obtained) (S1601). In this way, the musicpiece can be reproduced from the address specified by the user. Inaddition, the user can specify an address not only when the audio clientis in a reproducing state but also for example in a stop state or apause state.

2.7. Client with Automatic Connection Recovery Function

As described above, in the network type audio system, the audio clientis connected to the content server, and the content server reproducesmusic distributed from the content server. When abnormality in thecontent server during the distribution causes the audio client to bedisconnected from the content server, the audio client cannot reproducethe music until the audio client is once again connected to the contentserver. As for a typical audio client having an input device, the inputdevice is operated to allow the audio client to carry out connectionprocessing with the content server as shown in FIG. 5. The abovedescribed audio client stored in the outlet box without an input deviceis however left unconnected once it is disconnected from the contentserver. Therefore, the audio client desirably includes an automaticconnection recovery function as follows.

Referring to FIG. 115, the audio client Cj determines whether or not aprescribed time period has passed after its connection with the contentserver Si (S110). After the prescribed time period, the audio client Cjdetermines whether or not the connection with the content server Si ismaintained (S111, S112). More specifically, the audio client Cjtransmits a connection confirmation command to the content server Si(S111). If there is a response from the content server Si to the audioclient Cj for the connection confirmation command (S112), it isdetermined that the connection is maintained. Meanwhile, if there is noresponse or a transmission error is caused (S112), it is determined thatthe connection is cut off. As the response, for example the contentserver Si may return the command the same as the transmitted commandconfirmation command.

If there is a response in step S112, the audio client Cj again returnsto step S110 and determines whether or not the connection is maintainedafter a prescribed time period (S110 to S112). In this way, the audioclient Cj checks the connection state with the content server Si atprescribed intervals. If the connection is cut off, the audio client Cjretries to connect to the same content server Si (S12).

After the re-connecting attempt, if the audio client successfullyconnects with the content server Si (S113), the audio client Cjtransmits the client status immediately before the disconnection to thecontent server Si (S13). The client status includes for example areproducing state such as “reproducing,” “stop,” and “pause,” volumeinformation, and a list construction key. Therefore, the audio client Cjcan recover the original connection state with the content server Si.Consequently, the user can use the audio client Cj without being awarethat the audio client Cj has re-connected with the content server Si.

Meanwhile, after the re-connecting attempt, if the audio client cannotconnect with the content server Si (S113), the audio client Cj gives upreconnecting with the same content server Si and carries out connectionprocessing with another content server Si (S11 to S13). Morespecifically, the audio client Cj searches for a content server Si thatcan be connected by broadcasting (S11) and connects with the contentserver Si found by the searching (S12). After the connection, the audioclient Cj transmits the client status immediately before thedisconnection to the content server Si (S13).

The audio client Cj achieves the above described automatic connectionrecovery function by an installed connection recovery program in FIG.115.

By the above operation, the connection state is checked by the audioclient Cj at prescribed intervals, and if the connection is cut off, theaudio client Cj reestablishes connection. Therefore, if any abnormalityin the content server Si causes disconnection, the audio client Cj isnot left in the state disconnected from the content server Si. If anyabnormality in the content server Si prevents re-connection with thecontent server Si, the audio client connects with another content serverSi. Consequently, the user can always use the controller Ak to controlthe audio client Cj.

The audio client Cj transmits the client status immediately before thedisconnection to the content server Si connected at the moment, andtherefore the audio client Cj can connect with another content server Siand still regain the state immediately before the disconnection.Therefore, the user can use the audio client Cj without being aware ofthe disconnection between the audio client Cj and the content server Si.

According to the embodiment, the audio client Cj has an automaticconnection recovery function, but the controller Ak may have theautomatic connection recovery function. A passive client having only amusic reproducing function preferably has the automatic connectionrecovery function rather than an active client having both the musicreproducing function and the control function. This is because a passiveaudio client Cj without a control function does not transmit a commandto the content server Si on its own, and therefore once it isdisconnected from the content server Si, it is left as it is. Theconnection with the content server Si cannot be reestablished unless theuser reactivates the audio client Cj.

The steps according to all the embodiments described above formoperation programs that enable a computer to carry out the operation.Therefore, when the operation programs are installed in the contentservers Si, audio clients, controllers, and AVR clients, a network typeaudio system can be provided. The operation programs may directly bedistributed through a telecommunication line such as the Internet or maybe stored in a computer readable storage medium such as a CD-ROM and aDVD-ROM for distribution.

The embodiments of the invention have been shown and described simply byway of illustrating the present invention. Therefore, the invention isnot limited to the embodiments described above and various changes andmodifications may be made therein without departing from the scope ofthe invention.

1-143. (canceled)
 144. A network type content reproducing systemcomprising a server and at least one client connected to said server,said server comprising a storage device for storing a plurality ofcontents, said client comprising a content list requester requestingsaid server to provide a content list of a plurality of contents, saidserver further comprising a content list returner responsive to therequest from said first client and returning said content list, and saidclient further comprising a content list receiver receiving the contentlist returned from said server.
 145. The network type contentreproducing system according to claim 144, wherein said content listrequester requests said server to provide a specified amount of acontent list, and said content list returner returns said specifiedamount of the content list in response to the request from said client.146. The network type content reproducing system according to claim 145,wherein said content list requester transmits a list request commandincluding an obtaining start index indicating the first content to beobtained from said server by said client and an obtaining numberindicating the number of contents to be obtained from said server bysaid client, and said content list returner returns the content list ofcontents as many as said obtaining number starting from the firstcontent indicated by said obtaining start index in response to said listrequest command.
 147. The network type content reproducing systemaccording to claim 146, wherein said content list returner furtherreturns the number of contents included in said content list to bereturned and the number of the remaining contents left out of saidcontent list to be returned.
 148. The network type content reproducingsystem according to claim 144, wherein said client further comprises acategory list requester requesting said server to provide a categorylist of a plurality of categories, said server further comprises acategory list returner responsive to the request from said client andreturning said category list, said client further comprises a categorylist receiver receiving the category list returned from said server, andsaid content list requester selects a category of the contents in thecontent list to be requested in said received category list.
 149. Thenetwork type content reproducing system according to claim 144, whereinsaid content list requester transmits a list construction key necessaryfor producing said content list to said server, and said content listreturner produces said content list based on the list construction keytransmitted from said client.
 150. The network type content reproducingsystem comprising a server and at least one client connected to saidserver, said server comprising a storage device for storing a pluralityof contents, said client comprising content requester for requestingsaid server to provide a predetermined amount of a content selectedamong said plurality of contents, said server further comprising acontent returner responsive to the request from said client andreturning the predetermined amount of said selected content to saidclient, said client further comprising a reproducer reproducing thecontent returned from said server, and said content requester repeatsthe request for said content until said content is obtained in itsentirety.
 151. The network type content reproducing system according toclaim 150, wherein said client further comprises a buffer memory forstoring the content returned from said server, and said contentrequester requests said server to provide said predetermined amount ofthe content when a prescribed empty space is generated in said buffermemory.
 152. The network type content reproducing system according toclaim 150, wherein said content requester calculates an obtaining startaddress indicating the first address of said predetermined amount of thecontent and transmits a content transfer request command including theobtaining start address and an obtaining data length indicating thelength of the content to be obtained from said server by said client,and said content returner returns the content for said obtaining datalength from said obtaining start address, in response to said contenttransfer request command.
 153. The network type content reproducingsystem according to claim 152, wherein said content requester adds saidobtaining data length to the previous obtaining start address tocalculate the next obtaining start address.
 154. The network typecontent reproducing system according to claim 153, wherein said clientfurther comprises: a first setter setting first and second addresses;and a second setter setting said obtaining start address to said firstaddress when said calculated obtaining start address exceeds said secondaddress.
 155. The network type content reproducing system according toclaim 152, wherein said client further comprises; a first setter settinga desired address; and a second setter setting said obtaining startaddress to said desired address.
 156. The network type contentreproducing system according to claim 152, wherein said client furthercomprises: a setter setting a prescribed skip amount; and a shiftershifting said obtaining start address by said set skip amount.
 157. Thenetwork type content reproducing system according to claim 150, whereinsaid client further comprises a transmitter transmitting theidentification information of said selected content to said server, saidserver comprises a returner responsive to the identification informationtransmitted from said client and returning the offset of said selectedcontent to said client, and said client further comprises a detectordetecting the start of said selected content based on the offsetreturned from said server.
 158. The network type content reproducingsystem according to claim 150, wherein said client further comprises atransmitter transmitting the identification information of said selectedcontent to said server, said server further comprises a returnerresponsive to the identification information transmitted from saidclient and returning the size of said selected content to said client,and said client further comprises a detector detecting the end of saidselected content based on the size returned from said server.
 159. Anetwork type content reproducing system comprising a server and at leastone client connected to said server, said server comprising a storagedevice for storing a plurality of contents, said client comprisingcontent requester for calculating an obtaining start address indicatingthe first address of a content selected among said plurality of contentsand transmitting the obtaining start address to said server, said serverfurther comprising a content returner returning the content from theobtaining start address transmitted from said client, said clientfurther comprising a reproducer reproducing the content returned fromsaid server.
 160. A network type content reproducing system comprising aserver and at least one client connected to said server, said servercomprising a storage device for storing a plurality of contents, saidclient comprising content requester for requesting said server toprovide a specified amount of a content selected among said plurality ofcontents, said server further comprising a content returner responsiveto the request from said client and returning the specified amount ofsaid selected content to said client, said client further comprising areproducer reproducing the content returned from said server, and saidcontent requester changes the specified amount of the content to berequested to said server.
 161. The network type content reproducingsystem according to claim 160, wherein said content requester changesthe specified amount of the content to be requested to said server inresponse to the time between the request to said server for the contentand the receipt of said requested content.
 162. The network type contentreproducing system according to claim 160, wherein said contentrequester changes the specified amount of the content to be requested tosaid server in response to the data format of the content to berequested to said server.
 163. A network type content reproducing systemcomprising a server and at least one client connected to said server,said server comprising, a storage device for storing a plurality ofcontents, and a content transmitter transmitting a content selectedamong said plurality of contents to said client, and said client furthercomprising, a reproducer reproducing the content transmitted from saidserver, and a client information transmitter transmitting clientinformation related to said client to said server every time the clientinformation changes.
 164. A network type content reproducing systemcomprising a server and at least one first client connected to saidserver, said server comprising, a storage device for storing a pluralityof contents, and a content transmitter transmitting a content selectedamong said plurality of contents to said first client, said first clientcomprising a reproducer reproducing the content transmitted from saidserver, and said network type content reproducing system furthercomprising a second client connected to said server for monitoring saidfirst client.
 165. The network type content reproducing system accordingto claim 164, wherein said server comprises a client informationtransmitter transmitting client information related to said firstclient, to said second client, and said second client comprises areceiver receiving the client information transmitted from said server.166. The network type content reproducing system according to claim 165,wherein said server transmits said client information to said secondclient through a push port for forcing a request to be transmitted tosaid second client.
 167. The network type content reproducing systemaccording to claim 165, wherein said second client further comprises: adisplay displaying said received client information; and a changerchanging the display of said received client information when saidclient information is changed.
 168. The network type content reproducingsystem according to claim 165, wherein said second client furthercomprises a content list requester requesting said server to provide acontent list of a plurality of contents, said server further comprises acontent list returner responsive to the request from said second clientand returning said content list, and said second client furthercomprises a content list receiver receiving the content list returnedfrom said server.
 169. The network type content reproducing systemaccording to claim 168, wherein said client information includes a listconstruction key necessary for producing said content list, said contentlist requester transmits the list construction key included in saidreceived client information to said server when the list constructionkey is changed, and said content list returner produces said contentlist based on the list construction key transmitted from said secondclient.
 170. The network type content reproducing system according toclaim 165, wherein said second client receives the client informationtransmitted from said server when said second client is connected tosaid server.
 171. The network type content reproducing system accordingto claim 170, wherein said client information includes a listconstruction key necessary for producing said content list, said secondclient further comprises a content list requester requesting said serverto provide a content list of a plurality of contents to transmit thelist construction key included in said received client information tosaid server, and said server further comprises a content list returnerresponsive to the request from said second client and producing saidcontent list based on the list construction key transmitted from saidsecond client to return said content list to said second client. 172.The network type content reproducing system according to claim 165,wherein said client information includes the name of a data format of acontent reproducible by said first client, and said second clientcomprises a display displaying the name of said data format based onsaid received client information.
 173. The network type contentreproducing system according to claim 172, wherein said second clientfurther comprises: an obtainer obtaining a content list of a pluralityof contents from said server; and a display displaying a contentreproducible by said first client among the contents included in saidobtained content list and displaying a content that cannot be reproducedby said first client in a different manner from the reproducible contentor not displaying the irreproducible content.
 174. The network typecontent reproducing system according to claim 164, wherein said secondclient comprises a determiner determining whether a client to bemonitored is said first client.
 175. The network type contentreproducing system according to claim 164, wherein said second clientcomprises: an obtainer obtaining a monitoring handle necessary formonitoring said first client; and a monitor monitoring said first clientusing said obtained monitoring handle.
 176. The network type contentreproducing system according to claim 175, wherein said first clientfurther comprises a transmitter transmitting client information relatedto said first client to said server, said server comprises: a receiverreceiving the client information transmitted from said first client; adeterminer determining whether said second client has said monitoringhandle; and a transmitter transmitting said received client informationto said second client when said second client has said monitoring handlebased on the result of said determination, and said second clientcomprises a receiver receiving the client information transmitted fromsaid server.
 177. The network type content reproducing system accordingto claim 164, wherein said second client controls said first client.178. A network type content reproducing system comprising a server andat least one first client connected to said server, said servercomprising, a storage device for storing a plurality of contents, and acontent transmitter transmitting a content selected among said pluralityof contents to said first client, said first client comprising areproducer reproducing the content transmitted from said server, andsaid network type content reproducing system further comprising a secondclient connected to said server for controlling said first client. 179.The network type content reproducing system according to claim 178,wherein said second client comprises a server requester requesting saidserver to control said first client, and said server further comprises acontroller responsive to the request from said second client andcontrolling said first client.
 180. The network type content reproducingsystem according to claim 178, wherein said server controls said firstclient through a push port for forcing a request to be transmitted tosaid first client.
 181. The network type content reproducing systemaccording to claim 179, wherein said server requester transmitsinformation for specifying said first client and information forspecifying said selected content to said server.
 182. The network typecontent reproducing system according to claim 178, wherein said secondclient comprises a determiner determining whether a client to becontrolled is said first client.
 183. The network type contentreproducing system according to claim 178, wherein said second clientcomprises: a determiner determining whether the data format of saidselected content matches the data format of the content that can bereproduced by said first client; and an instructor instructing saidfirst client to reproduce said selected content when said data formatsmatch.
 184. The network type content reproducing system according toclaim 178, wherein said second client comprises: an obtainer obtaining acontrol handle necessary for controlling said first client; and acontroller controlling said first client using said obtained controlhandle.
 185. The network type content reproducing system according toclaim 184, wherein said second client further comprises a requesterrequesting said server to issue a server request to said first client,and said server comprises a determiner determining whether or not saidsecond client has said control handle when said second client requestssaid server to issue the server request; and a transmitter transmittingsaid server request to said first client when said second client hassaid control handle based on the result of said determination.
 186. Thenetwork type content reproducing system according to claim 178, whereinsaid first client further comprises a transmitter transmitting acompletion status to said server when said first client finishesreproducing a content as instructed by said second client andtransmitting a stop status different from said completion status to saidserver when said first client finishes reproducing a content selected bysaid first client or stops reproducing the content midway in response tothe operation of the user.
 187. The network type content reproducingsystem according to claim 178, wherein said server comprises a receiverreceiving the completion status transmitted from said first client andtransmitting the completion status to said second client, and saidsecond client comprises an instructor responsive to the completionstatus transmitted from said server and instructing said first client toreproduce the content next to the content that has been reproduced tothe end.
 188. A network type content reproducing system comprising aserver and at least one client connected to said server, said clientfurther comprising a broadcaster broadcasting prescribed information,said server comprising a returner responsive to the prescribedinformation broadcasted from said client and returning server specifyinginformation to specify said server to said client, and said clientcomprising a receiver receiving the server specifying informationreturned from said server and registering the information in a serverlist.
 189. The network type content reproducing system according toclaim 188, wherein said client further comprises a determinerdetermining whether said server specifying information is registered insaid server list, and when said server specifying information is notregistered in said server list based on the result of saiddetermination, said broadcaster broadcasts said prescribed informationagain.
 190. The network type content reproducing system according toclaim 189, wherein said client further comprises an accessor accessing aserver on the Internet when the number of broadcasting operation by saidbroadcaster reaches a prescribed number of times or time forbroadcasting by said broadcaster reaches a prescribed time period. 191.The network type content reproducing system comprising a server and atleast one client connected to said server, said client comprising, afirst establisher establishing connection at a command port fortransmitting/receiving a command between said server and said client;and a second establisher establishing connection at a push port forforcing a request to be transmitted to said client from said server.192. The network type content reproducing system according to claim 191,wherein said client further comprises a transmitter transmitting aclient index request command to said server through said command port,said client index request command being necessary for identifying saidclient, said server further comprises a returner responsive to theclient index request command transmitted from said client and returningsaid client index to said client, and said client further comprises atransmitter transmitting the client index returned from said server tosaid server through said push port.
 193. The network type contentreproducing system according to claim 191, wherein there are a pluralityof said clients, and said server comprises a connection limiter limitingthe number of connectable clients.
 194. The network type contentreproducing system according to claim 193, wherein said connectionlimiter disconnects from said client that has been already connectedbased on a prescribed priority order when another said client that hasnot yet been connected tries to be connected.
 195. A network typecontent reproducing system, comprising: a server; a first clientconnected to said server; AV equipment connected to said first client;and a second client connected to said server to control said AVequipment, said second client comprising a transmitter transmitting acontrol command for controlling said AV equipment to said server, saidserver comprising a transmitter transmitting the control commandtransmitted from said second client to said first client, said firstclient comprising a transmitter transmitting the control commandtransmitted from said server to said AV equipment, said AV equipmentbeing controlled in response to the control command transmitted fromsaid first client.
 196. The network type content reproducing systemaccording to claim 195, wherein said AV equipment comprises: acontrollable element; and a controller responsive to the control commandtransmitted from said first client and controlling said element.
 197. Anetwork type content reproducing system comprising a server and at leastone client connected to said server, said server comprising, a storagedevice for storing a plurality of contents, and a content transmittertransmitting a content selected among said plurality of contents to saidclient, said network type content reproducing system further comprisingAV equipment connected to said client, said client comprising atransmitter transmits content transmitted from said server to said AVequipment, and said AV equipment comprising a reproducer reproducing acontent transmitted from said client.
 198. A network type contentreproducing system, comprising: a server; a first client connected tosaid server; AV equipment connected to said first client; and a secondclient connected to said server to monitor said AV equipment, said AVequipment comprising a transmitter transmitting information related tosaid AV equipment to said first client, said first client comprising anAV equipment information transmitter transmitting the informationtransmitted from said AV equipment to said server, said servercomprising a transmitter transmitting the information transmitted fromsaid first client to said second client.
 199. The network type contentreproducing system according to claim 198, wherein said informationfrequently changes, and the AV equipment information transmitter of saidfirst client transmits said information at prescribed intervals.
 200. Anetwork type content reproducing system comprising a server and at leastone first client connected to said server, said server comprising, astorage device for storing a plurality of contents, and a contenttransmitter transmitting a content selected among said plurality ofcontents to said first client, said first client comprising a reproducerreproducing the content transmitted from said server, and said serverfurther comprising a firmware updater updating firmware in said firstclient.
 201. The network type content reproducing system according toclaim 200, wherein said server further comprises: a register registeringinformation related to a plurality of firmware pieces suitable for saidfirst client; and a firmware list transmitter transmitting a firmwarelist of said registered information related to the plurality of firmwarepieces to said first client, said first client further comprises: areceiver receiving the firmware list transmitted from said server; and afirmware requester for requesting said server to transmit firmwareselected in said received firmware list, and said firmware updaterreturns said selected firmware to said first client in response to therequest from said first client.
 202. The network type contentreproducing system according to claim 201, wherein said first clientfurther comprises a transmitter transmitting client information relatedto said first client to said server, and said server further comprises aproducer producing said firmware list based on the client informationtransmitted from said first client.
 203. The network type contentreproducing system according to claim 200, wherein said first clientrequests said server to provide a specified amount of firmware; and saidfirmware updater returns said specified amount of the firmware inresponse to the request from said first client.
 204. The network typecontent reproducing system according to claim 203, wherein said firstclient transmits an obtaining start address indicating the first addresswhere firmware to be obtained from said server by said first client isstored and an obtaining data length indicating the length of firmware tobe obtained from said server by said first client, and said firmwareupdater responds to the request from said first client to return thefirmware for said obtaining data length from said obtaining startaddress.
 205. The network type content reproducing system according toclaim 200, wherein said server further comprises a requester requestingsaid first client to update firmware and transmitting informationrelated to the firmware to said first client.
 206. The network typecontent reproducing system according to claim 201, wherein said firstclient further comprises a firmware list requester requesting saidserver to provide a specified amount of a firmware list, and saidfirmware list transmitter transmits said specified amount of thefirmware list to said first client in response to the request from saidfirst client.
 207. The network type content reproducing system accordingto claim 206, wherein said firmware list requester transmits a firmwarelist request command including an obtaining start index indicating thefirst firmware information to be obtained from said server by said firstclient and an obtaining number indicating the number of pieces of thefirmware information to be obtained from said server by said firstclient, and said firmware list transmitter transmits a firmware listincluding pieces of the firmware information as many as said obtainingnumber from the first firmware information indicated by said obtainingstart index in response to said firmware list request command.
 208. Thenetwork type content reproducing system according to claim 200, furthercomprising a second client connected to said server to control saidfirst client, wherein said second client comprises a requesterrequesting said server to update firmware in said first client.
 209. Anetwork type content reproducing system, comprising a server, a firstclient connected to said server, and a plurality of second clientsconnected to said server, said server comprising a content storagedevice for storing a plurality of contents, said second clients eachcomprising a specifier specifying a content among said plurality ofcontents and instructing said first client to reproduce the specifiedcontent, said first client comprising: a reproducer responsive to theinstruction from said second client and reproducing said specifiedcontent; and a transmitter transmitting a completion status to saidserver when said content has been reproduced to its end, said serverfurther comprising a status transmitter selecting one of said pluralityof second clients and transmitting the completion status to saidselected second client in response to the completion status receivedfrom said first client, said second clients each comprising a specifierspecifying a content next to the content that has been reproduced to itsend by said first client and instructing said first client to reproducethe specified content in response to the completion status received fromsaid server.
 210. The network type content reproducing system accordingto claim 209, wherein said server further comprises a manager managingthe priorities of the second clients that can control said first client,and said status transmitter selects a second client with the highestpriority as the second client to receive said transmitted completionstatus.
 211. The network type content reproducing system according toclaim 210, wherein said status transmitter transmits a stop status tothe second client other than the second client with the highestpriority.
 212. The network type content reproducing system according toclaim 209, wherein said server further comprises a memory for storingthe identification information of said second client that has instructedreproduction, and said status transmitter selects said second clientthat has instructed reproduction as the second client to receive saidcompletion status based on said stored identification information of thesecond client.
 213. The network type content reproducing systemaccording to claim 212, wherein said status transmitter transmits a stopstatus to the second client other than said selected second client. 214.A network type content reproducing system comprising a server, a firstclient connected to said server, and a plurality of second clientsconnected to said server, said server comprising a content storagedevice for storing a plurality of contents, said second clients eachcomprising: a control handle obtainer obtaining a control handlenecessary for controlling said first client; and a specifier specifyinga content among said plurality of contents after obtaining said controlhandle and instructing said first client to reproduce the specifiedcontent, said first client comprising a reproducer responsive to theinstruction from said second client and reproducing said specifiedcontent; and a transmitter transmitting a completion status to saidserver when said content has been reproduced to its end, said serverfurther comprising a transfer transferring the completion statustransmitted from said first client to each of said second clients, andsaid second clients each further comprising a specifier specifying acontent next to the content that has been reproduced to its end by saidfirst client in response to the completion status received from saidfirst client whose control handle is obtained by the second client andinstructing said first client to reproduce the specified content. 215.The network type content reproducing system according to claim 214,wherein said control handle obtainer, upon obtaining said controlhandle, prohibits the other second client from obtaining said controlhandle.
 216. The network type content reproducing system according toclaim 215, wherein said first client further comprises a transmittertransmitting a stop status to said server when said first client stopsreproducing said content midway, said server further comprises atransfer transferring the stop status transmitted from said first clientto each of said second clients, and said second clients each furthercomprise a canceller canceling the prohibition of obtaining said controlhandle in response to the stop status received from the first clientwhose control handle is obtained by said second client.
 217. A networktype content reproducing system comprising a server, a first clientconnected to said server, and a second client connected to said server,said server comprising a content storage device for storing a pluralityof contents, said second client comprising a specifier specifying acontent among said plurality of contents and instructing said firstclient to reproduce the specified content, said first client comprising:a reproducer responsive to the instruction from said second client andreproducing said specified content; and a transmitter transmitting acompletion status to said server when said content has been reproducedto its end, said server further comprising a continuous reproducinginstructor responsive to the completion status received from said firstclient and specifying a content next to the content that has beenreproduced to its end by said first client and instructing said firstclient to reproduce the specified content.
 218. The network type contentreproducing system according to claim 217, wherein said server furthercomprises: a memory for storing a list construction key necessary forproducing a content list of contents to be reproduced by said firstclient; and a producer producing said content list based on said listconstruction key, and said continuous reproducing instructor instructssaid first client to reproduce said content according to said contentlist.
 219. A network type content reproducing system comprising aserver, a first client connected to said server, and a second clientconnected to said server, said server comprising a content storagedevice for storing a plurality of contents, said second clientcomprising: a specifier specifying a content among said plurality ofcontents and instructing said first client to reproduce the specifiedcontent; and a transmitter transmitting a list construction keynecessary for producing a content list of contents to be reproduced bysaid first client to said first client, said first client comprising: areproducer responsive to the instruction from said second client andreproducing said specified content; and a transmitter transmitting thelist construction key transmitted from said second client to saidserver, said server further comprising a producer producing said contentlist based on the list construction key transmitted from said secondclient and transmitting the produced content list to said first client,said first client further comprising a reproducer reproducing a contentnext to the content that has been reproduced to its end by said firstclient according to the content list transmitted from said server. 220.A server connectable to client comprising: a storage device for storinga plurality of contents; and a content list returner responsive to arequest from said client and returning a content list of a plurality ofcontents.
 221. The server according to claim 220, wherein said contentlist returner returns a specified amount of a content list in responseto the request from said client.
 222. The server according to claim 221,wherein said content list returner responds to a list request commandfrom said client, said command including an obtaining start indexindicating the first content to be obtained from said server by saidclient and an obtaining number indicating the number of contents to beobtained from said server by said client and returns a content list ofcontents as many as said obtaining number from the first contentindicated by said obtaining start index.
 223. The server according toclaim 222, wherein said content list returner further returns the numberof contents included in said content list to be returned and the numberof the remaining contents left out of said content list to be returned.224. The server according to claim 220, further comprising a returnerresponsive to a request from said client and returning a category listof a plurality of categories.
 225. The server according to claim 220,wherein said content list returner produces said content list based onthe list construction key transmitted from said client.
 226. A serverconnectable to client comprising: a storage device for storing aplurality of contents; and a content returner repeating returning apredetermined amount of a content selected among said plurality ofcontents in response to a request from said client, so that said contentis returned in its entirety.
 227. The server according to claim 226,wherein said content returner responds to a content transfer requestcommand transmitted from said client, said command including anobtaining start address indicating the first address where a content tobe obtained from said server by said client is stored and an obtainingdata length indicating the length of the content to be obtained fromsaid server by said first client and returns a content for saidobtaining data length from said obtaining start address.
 228. The serveraccording to claim 226, further comprising a returner responsive to theidentification information of said selected content transmitted fromsaid client and returning the offset of said selected content to saidclient.
 229. The server according to claim 226, further comprising areturner responsive to the identification information of said selectedcontent transmitted from said client and returning the size of saidselected content to said client.
 230. A server connectable to a firstclient and a second client controlling said first client, comprising: acontroller responsive to a request from said second client andcontrolling said first client.
 231. A server connectable to a clientcomprising: a storage device for storing a plurality of contents, acontent transmitter transmitting a content selected among said pluralityof contents to said client, and firmware updater for updating firmwarein said client.
 232. The server according to claim 231 furthercomprising: a register registering the information related to aplurality of firmware pieces suitable for said client; and a firmwarelist transmitter for transmitting a firmware list of said registeredinformation of the plurality of firmware pieces to said client, saidfirmware updater returning firmware selected in said firmware list tosaid client in response to a request from said client.
 233. The serveraccording to claim 231, wherein said firmware updater transmits aspecified amount of firmware requested by said client to said client.234. The server according to claim 233, wherein said firmware updaterreturns firmware for an obtaining data length indicating the length offirmware to be obtained by said client from an obtaining start addressindicating the first address where the firmware to be obtained by saidclient is stored.
 235. The server according to claim 232, wherein saidfirmware list transmitter transmits a specified amount of a firmwarelist requested by said client to said client.
 236. The server accordingto claim 235, wherein said firmware list transmitter responds to afirmware list request command from said client, said command includingan obtaining start index indicating the first firmware information to beobtained from said server by said client and an obtaining numberindicating the number of pieces of firmware information to be obtainedfrom said server by said client and transmits a firmware list includingpieces of the firmware information as many as said obtaining number fromsaid first firmware information indicated by said obtaining start indexto said client.
 237. A client connectable to a server and buried in anoutlet box provided in a wall.
 238. A client connectable to a servercomprising: a content list requester requesting said server to provide acontent list of a plurality of contents stored in said server; and acontent list receiver receiving the content list returned from saidserver in response to said request.
 239. The client according to claim238, wherein said content list requester requests said server to providea specified amount of a content list.
 240. The client according to claim239, wherein said content list requester transmits a list requestcommand including an obtaining start index indicating the first contentto be obtained from said server by said client and an obtaining numberindicating the number of contents to be obtained from said server bysaid client, and said content list receiver receives a content listreturned from said server in response to said list request command, saidcontent list of contents as many as said obtaining number from the firstcontent indicated by said obtaining start index.
 241. The clientaccording to claim 238, further comprising: a category list requesterrequesting said server to provide a category list of a plurality ofcategories; and a receiver receiving the category list returned fromsaid server in response to said request, said content list requesterselecting a category of the contents in the content list to be requestedin said received category list.
 242. The client according to claim 238,wherein said content list requester transmits a list construction keynecessary for producing said content list to said server.
 243. A clientconnectable to a server comprising: a content requester for requestingsaid server to provide a predetermined amount of a content selectedamong a plurality of contents stored in said server; a reproducerreproducing the content transmitted from said server in response to saidrequest, and said content requester repeating the request for saidcontent until said content is obtained in its entirety.
 244. The clientaccording to claim 243, further comprising a buffer memory storing thecontent returned from said server, wherein said content requesterrequests said server to provide said predetermined amount of the contentwhen a prescribed empty space is generated in said buffer memory. 245.The client according to claim 243, wherein said content requestercalculates an obtaining start address indicating the first address ofsaid predetermined amount of the content and transmits a contenttransfer request command including the calculated obtaining startaddress and an obtaining data length indicating the length of thecontent to be obtained from said server by said client.
 246. The clientaccording to claim 245, wherein said content requester adds saidobtaining data length to the previous obtaining start address tocalculate the next obtaining start address.
 247. The client according toclaim 246, further comprising: a first setter setting first and secondaddresses; and a second setter setting said obtaining start address tosaid first address when said calculated obtaining start address exceedssaid second address.
 248. The client according to claim 245, furthercomprising: a first setter setting a desired address; and a secondsetter setting said obtaining start address to said desired address.249. The client according to claim 245 further comprising: a settersetting a prescribed skip amount; and a shifter shifting said obtainingstart address by said set skip amount.
 250. The client according toclaim 243, further comprising: a transmitter transmitting theidentification information of said selected content to said server; anda detector detecting the start of said selected content based on theoffset of said selected content returned from said server in response tosaid identification information.
 251. The client according to claim 243,further comprising: a transmitter transmitting the identificationinformation of said selected content to said server; and a detectordetecting the end of said selected content based on the size of saidselected content returned from said server in response to saididentification information.
 252. A client connectable to a servercomprising: a content requester for calculating an obtaining startaddress indicating the first address of a content selected among aplurality of contents stored in said server and transmitting theobtaining start address to said server, and a reproducer reproducing thecontent returned from said server in response to said transmittedobtaining start address.
 253. A client connectable to a servercomprising: a content requester for requesting said server to provide aspecified amount of a content selected among a plurality of contentsstored in said server; and a reproducer reproducing the content returnedfrom said server in response to said request; and said content requesterchanging the specified amount of the content to be requested to saidserver.
 254. A client connectable to a server comprising: a reproducerreproducing a content transmitted from said server; and a transmittertransmitting client information related to said client to said serverevery time the client information changes.
 255. A client connectable toa server comprising: a firmware requester for requesting said server totransmit firmware.
 256. The client according to claim 255, furthercomprising a receiver receiving a firmware list transmitted from saidserver, wherein said firmware requester selects firmware to betransmitted in said received firmware list.
 257. The client according toclaim 255, wherein said firmware requester requests said server toprovide a specified amount of firmware.
 258. The client according toclaim 257, wherein said firmware requester transmits an obtaining startaddress indicating the first address where firmware to be obtained fromsaid server is stored and an obtaining data length indicating the lengthof the firmware to be obtained from said server.
 259. The clientaccording to claim 255 further comprising a firmware list requester forrequesting said server to provide a specified amount of a firmware list.260. The client according to claim 259, wherein said firmware listrequester transmits a firmware list request command including anobtaining start index indicating the first firmware information to beobtained from said server and an obtaining number indicating the numberof pieces of firmware information to be obtained from said server. 261.The client connectable to a plurality of servers, comprising: aconnecter connecting with any one of said plurality of servers; and adeterminer for determining whether connection with the server by saidconnecter is maintained at prescribed intervals, said connecterreestablishing connection with said server when said determinerdetermines that the connection is closed.
 262. The client according toclaim 261, wherein said connecter establishes connection with anotherserver when the connection with said server cannot be reestablished.263. The client according to claim 261, wherein said connecter transmitsa client status before the connection is closed to the connected server.264. A monitoring client monitoring a reproducing client reproducing acontent transmitted from a server, and said monitoring clientconnectable to said server comprising: a receiver receiving the clientinformation related to said reproducing client transmitted from saidserver; and a display displaying said received client information. 265.The monitoring client according to claim 264, further comprising achanger changing the display of said received client information whensaid client information is changed.
 266. The monitoring client accordingto claim 264, wherein said client information includes the name of adata format of a content reproducible by said reproducing client, saidmonitoring client further comprising a display displaying the name ofsaid data format based on said received client information.
 267. Themonitoring client according to claim 266, further comprising: anobtainer obtaining a content list of a plurality of contents from saidserver; and a display displaying a content reproducible by saidreproducing client among the contents included in said obtained contentlist and displaying a content that cannot be reproduced by saidreproducing client in a different manner from the reproducible contentor not displaying the irreproducible content.
 268. The monitoring clientaccording to claim 264, further comprising a determiner determiningwhether a client to be monitored is said reproducing client.
 269. Themonitoring client according to claim 264, further comprising: anobtainer obtaining a monitoring handle necessary for monitoring saidreproducing client; and a moitor monitoring said reproducing clientusing said obtained monitoring handle.
 270. A server connectable to afirst client reproducing a content and a second client monitoring saidfirst client, comprising: a storage device for storing a plurality ofcontents; a content transmitter transmitting a content selected amongsaid plurality of contents to said first client; and a clientinformation transmitter transmitting client information related to saidfirst client, to said second client.
 271. The server according to claim270, wherein said client information transmitter transmits said clientinformation to said second client through a push port for forcing arequest to be transmitted to said second client.
 272. The serveraccording to claim 270, further comprising: a content list returnerresponsive to the request from said second client and returning acontent list of said plurality of contents.
 273. The server according toclaim 272, wherein said client information includes a list constructionkey necessary for producing said content list, and said content listreturner produces said content list based on the list construction keytransmitted from said second client.
 274. A monitoring client monitoringa reproducing client reproducing a content transmitted from a server andconnectable to said server, comprising: a client information receiverfor receiving client information related to said reproducing client fromsaid server; a content list requester requesting said server to providea content list of a plurality of contents, and a content list receiverreceiving the content list returned from said server.
 275. Themonitoring client according to claim 274, wherein said clientinformation includes a list construction key necessary for producingsaid content list, and said content list requester transmits the listconstruction key included in said received client information to saidserver when the list construction key is changed.
 276. The monitoringclient according to claim 274, wherein said client information receiverreceives said client information when said monitoring client isconnected to said server.
 277. The monitoring client according to claim276, wherein said client information includes a list construction keynecessary for producing said content list, said content list requestertransmits the list construction key included in said received clientinformation to said server.
 278. A server connectable to a first clientreproducing a content and a second client monitoring said first clientusing an obtained monitoring handle necessary for monitoring said firstclient, comprising: a storage device for storing a plurality ofcontents; a content transmitter transmitting a content selected amongsaid plurality of contents to said first client; a determinerdetermining whether said second client has said monitoring handle; and atransmitter transmitting client information related to said firstclient, to said second client when said second client has saidmonitoring handle based on the result of said determination.
 279. Acontrol client controlling a reproducing client reproducing a contenttransmitted from a server and connectable to said server, comprising: aserver requester for requesting said server to control said reproducingclient.
 280. The control client according to claim 279, wherein saidserver requester transmits information for specifying said reproducingclient and information for specifying said content to said server. 281.The server according to claim 230, wherein said controller controls saidfirst client through a push port for forcing a request to be transmittedto said first client.
 282. The control client according to claim 279,further comprising: a determiner determining whether a client to becontrolled is said reproducing client, and a controller controlling saidreproducing client when said reproducing client is to be controlledbased on the result of said determination
 283. The control clientaccording to claim 279, further comprising: a determiner determiningwhether the data format of said content matches the data format of thecontent that can be reproduced by said reproducing client; and aninstructor instructing said reproducing client to reproduce said contentwhen said data formats match.
 284. The control client according to claim279, further comprising: an obtainer obtaining a control handlenecessary for controlling said reproducing client; and a controllercontrolling said reproducing client using said obtained control handle.285. A server connectable to a first client reproducing a content and asecond client controlling said first client, comprising: a storagedevice for storing a plurality of contents; a content transmittertransmitting a content selected among said plurality of contents to saidfirst client; a determiner determining whether or not said second clienthas a control handle necessary for controlling said first client whensaid second client requests said server to issue a server request; and atransmitter transmitting said server request to said first client whensaid second client has said control handle based on the result of saiddetermination.
 286. The control client according to claim 279, furthercomprising: a receiver receiving a completion status transmitted fromsaid reproducing client through said server; and an instructorresponsive to said received completion status and instructing saidreproducing client to reproduce the content next to the content that hasbeen reproduced to the end.
 287. An AV equipment being controlled by afirst client connected to a server and connectable to a second clientconnected to said server, comprising: a controllable element; a receiverreceiving a control command transmitted from said first client throughsaid server and said second client: and a controller responsive to saidreceived control command and controlling said element.
 288. An AVequipment connectable to a relay client connected to a server,comprising: a receiver receiving a content selected among a plurality ofcontents stored in said server from said server through said relayclient: and a reproducer reproducing said received content.
 289. The AVequipment according to claim 288, further comprising: a transmittertransmitting information related to said AV equipment to a monitoringclient monitoring said AV equipment through said relay client and saidserver.
 290. A server connectable to a first client reproducing acontent and a plurality of second clients instructing said first clientto reproduce the content, comprising: a content storage device forstoring a plurality of contents, a content transmitter transmitting acontent selected among said plurality of contents to said first client;a status transmitter selecting one of said plurality of second clientsand transmitting a completion status indicating completion ofreproducing the content to the selected second client when receiving thecompletion status from said first client.
 291. The server according toclaim 290, further comprising: a manager managing the priorities of thesecond clients that can control said first client, and said statustransmitter selects a second client with the highest priority as thesecond client to receive said transmitted completion status.
 292. Theserver according to claim 291, wherein said status transmitter transmitsa stop status to the second client other than the second client with thehighest priority.
 293. The server according to claim 290, furthercomprising: a memory for storing the identification information of saidsecond client that has instructed reproduction, and said statustransmitter selects said second client that has instructed reproductionas the second client to receive said completion status based on saidstored identification information of the second client.
 294. The serveraccording to claim 293, wherein said status transmitter transmits a stopstatus to the second client other than said selected second client. 295.A control client controlling a reproducing client reproducing a contenttransmitted from a server and connectable to said server, comprising: acontrol handle obtainer obtaining a control handle necessary forcontrolling said reproducing client; a specifier specifying a contentamong a plurality of contents stored in said server after obtaining saidcontrol handle and instructing said reproducing client to reproduce thespecified content, and a specifier specifying a content next to thecontent that has been reproduced to its end by said reproducing clientin response to a completion status indicating completion of reproducingthe content received from said reproducing client whose control handleis obtained by said control client and instructing said reproducingclient to reproduce the specified content.
 296. The control clientaccording to claim 295, wherein said control handle obtainer, uponobtaining said control handle, prohibits the other control client fromobtaining said control handle.
 297. The control client according toclaim 296, further comprising: a canceller canceling the prohibition ofobtaining said control handle in response to a stop status indicatingstop of reproducing the content midway, said stop status received fromthe reproducing client whose control handle is obtained by said controlclient.
 298. A server connectable to a first client reproducing acontent and a second client instructing said first client to reproducethe content, comprising: a content storage device for storing aplurality of contents; a content transmitter transmitting a contentselected among said plurality of contents to said first client; and acontinuous reproducing instructor responsive to a completion statusindicating completion of reproducing the content, said completion statusreceived from said first client, specifying a content next to thecontent that has been reproduced to its end by said first client andinstructing said first client to reproduce the specified content. 299.The server according to claim 298, further comprising: a memory forstoring a list construction key necessary for producing a content listof contents to be reproduced by said first client; and a producerproducing said content list based on said list construction key, andsaid continuous reproducing instructor instructing said first client toreproduce said content according to said content list.
 300. Areproducing client being controlled by a control client connected to aserver and connectable to said server, comprising: a reproducerresponsive to an instruction from said control client and reproducing acontent specified among a plurality of contents stored in said server; afirst receiver receiving a -list construction key necessary forproducing a content list from said control client and transmitting thelist construction key to said server; a second receiver receiving thecontent list produced based on said transmitted list construction keyfrom said server; and a reproducer reproducing a content next to thecontent that has been reproduced to its end according to said receivedcontent list.
 301. A reproducing client being controlled by a controlclient connected to a server and connectable to said server, comprising:a reproducer reproducing a content transmitted from said server; and atransmitter transmitting a completion status to said server whenfinished reproducing a content as instructed by said control client andtransmitting a stop status different from said completion status to saidserver when finished reproducing a content selected by said reproducingclient or stopped reproducing the content midway in response to theoperation of the user.
 302. The network type content reproducing systemaccording to claim 165, wherein said first client further comprises atransmitter transmitting client information related to said first clientto said server, said server further comprises a receiver receiving theclient information transmitted from said first client, and said clientinformation transmitter transmits said received client information tosaid second client.
 303. The server according to claim 270, furthercomprising: a receiver receiving client information related to saidfirst client from said first client, and said client informationtransmitter transmitting said received client information to said secondclient.
 304. A computer program product causing a server connectable toa client to perform the steps of storing a plurality of contents in astorage device; and returning a content list of a plurality of contentsin response to a request from said client.
 305. The computer programproduct according to claim 304, wherein said step of returning returns aspecified amount of a content list in response to the request from saidclient.
 306. The computer program product according to claim 305,wherein said step of returning responds to a list request command fromsaid client, said command including an obtaining start index indicatingthe first content to be obtained from said server by said client and anobtaining number indicating the number of contents to be obtained fromsaid server by said client and returns a content list of contents asmany as said obtaining number from the first content indicated by saidobtaining start index.
 307. The computer program product according toclaim 306, wherein said step of returning further returns the number ofcontents included in said content list to be returned and the number ofthe remaining contents left out of said content list to be returned.308. The computer program product according to claim 304, furthercausing said server to perform the step of returning a category list ofa plurality of categories in response to a request from said client.309. The computer program product according to claim 304, wherein saidstep of returning produces said content list based on the listconstruction key transmitted from said client.
 310. A computer programproduct caused a server connectable to client to perform the steps of:storing a plurality of contents in a storage device; and repeatingreturning a predetermined amount of a content selected among saidplurality of contents in response to a request from said client, so thatsaid content is returned in its entirety.
 311. The computer programproduct according to claim 310, wherein said step of repeating respondsto a content transfer request command transmitted from said client, saidcommand including an obtaining start address indicating the firstaddress where a content to be obtained from said server by said clientis stored and an obtaining data length indicating the length of thecontent to be obtained from said server by said first client and returnsa content for said obtaining data length from said obtaining startaddress.
 312. The computer program product according to claim 310,further causing said server to perform the step of returning the offsetof said selected content to said client in response to theidentification information of said selected content transmitted fromsaid client.
 313. The computer program product according to claim 310,further causing said server to perform the step of returning the size ofsaid selected content to said client in response to the identificationinformation of said selected content transmitted from said client. 314.A computer program product causing a server connectable to a firstclient and a second client controlling said first client, to perform thestep of: controlling said first client in response to a request fromsaid second client.
 315. A computer program product causing a serverconnectable to a client to perform the steps of: storing a plurality ofcontents in a storage device; transmitting a content selected among saidplurality of contents to said client, and updating firmware in saidclient.
 316. The computer program product according to claim 315,further causing said server to perform the steps of registering theinformation related to a plurality of firmware pieces suitable for saidclient; and transmitting a firmware list of said registered informationof the plurality of firmware pieces to said client, said step ofupdating returning firmware selected in said firmware list to saidclient in response to a request from said client.
 317. The computerprogram product according to claim 315, wherein said step of updatingtransmits a specified amount of firmware requested by said client tosaid client.
 318. The computer program product according to claim 317,wherein said step of updating returns firmware for an obtaining datalength indicating the length of firmware to be obtained by said clientfrom an obtaining start address indicating the first address where thefirmware to be obtained by said client is stored.
 319. The computerprogram product according to claim 316, wherein said step oftransmitting transmits a specified amount of a firmware list requestedby said client to said client.
 320. The computer program productaccording to claim 319, wherein said step of transmitting responds to afirmware list request command from said client, said command includingan obtaining start index indicating the first firmware information to beobtained from said server by said client and an obtaining numberindicating the number of pieces of firmware information to be obtainedfrom said server by said client and transmits a firmware list includingpieces of the firmware information as many as said obtaining number fromsaid first firmware information indicated by said obtaining start indexto said client.
 321. A computer program product causing a clientconnectable to a server to perform the steps of requesting said serverto provide a content list of a plurality of contents stored in saidserver; and receiving the content list returned from said server inresponse to said request.
 322. The computer program product according toclaim 321, wherein said step of requesting requests said server toprovide a specified amount of a content list.
 323. The computer programproduct according to claim 322, wherein said step of requestingtransmits a list request command including an obtaining start indexindicating the first content to be obtained from said server by saidclient and an obtaining number indicating the number of contents to beobtained from said server by said client, and said step of receivingreceives a content list returned from said server in response to saidlist request command, said content list of contents as many as saidobtaining number from the first content indicated by said obtainingstart index.
 324. The computer program product according to claim 321,further causing said client to perform the step of: requesting saidserver to provide a category list of a plurality of categories; andreceiving the category list returned from said server in response tosaid request, said step of requesting selecting a category of thecontents in the content list to be requested in said received categorylist.
 325. The computer program product according to claim 321, whereinsaid step of requesting transmits a list construction key necessary forproducing said content list to said server.
 326. A computer programproduct causing a client connectable to a server to perform the stepsof: requesting said server to provide a predetermined amount of acontent selected among a plurality of contents stored in said server;reproducing the content transmitted from said server in response to saidrequest, and said step of requesting repeating the request for saidcontent until said content is obtained in its entirety.
 327. Thecomputer program product according to claim 326, further caused saidclient to perform the step of storing the content returned from saidserver in a buffer memory, wherein said step of requesting requests saidserver to provide said predetermined amount of the content when aprescribed empty space is generated in said buffer memory.
 328. Thecomputer program product according to claim 326, wherein said step ofrequesting calculates an obtaining start address indicating the firstaddress of said predetermined amount of the content and transmits acontent transfer request command including the calculated obtainingstart address and an obtaining data length indicating the length of thecontent to be obtained from said server by said client.
 329. Thecomputer program product according to claim 328, wherein said step ofrequesting adds said obtaining data length to the previous obtainingstart address to calculate the next obtaining start address.
 330. Thecomputer program product according to claim 329, further causing saidclient to perform the steps of: setting first and second addresses; andsetting said obtaining start address to said first address when saidcalculated obtaining start address exceeds said second address.
 331. Thecomputer program product according to claim 328, further causing saidclient to perform the steps of: setting a desired address; and settingsaid obtaining start address to said desired address.
 332. The computerprogram product according to claim 328 further causing said client toperform the steps of: setting a prescribed skip amount; and shiftingsaid obtaining start address by said set skip amount.
 333. The computerprogram product according to claim 326, further causing said client toperform the steps of transmitting the identification information of saidselected content to said server; and detecting the start of saidselected content based on the offset of said selected content returnedfrom said server in response to said identification information. 334.The computer program product according to claim 326, further causingsaid client to perform the steps of: transmitting the identificationinformation of said selected content to said server; and detecting theend of said selected content based on the size of said selected contentreturned from said server in response to said identificationinformation.
 335. A computer program product causing a clientconnectable to a server to perform the steps of: calculating anobtaining start address indicating the first address of a contentselected among a plurality of contents stored in said server andtransmitting the obtaining start address to said server, and reproducingthe content returned from said server in response to said transmittedobtaining start address.
 336. A computer program product causing aclient connectable to a server to perform the steps of: requesting saidserver to provide a specified amount of a content selected among aplurality of contents stored in said server; and reproducing the contentreturned from said server in response to said request; and said step ofrequesting changing the specified amount of the content to be requestedto said server.
 337. A computer program product causing a clientconnectable to a server to perform the steps of reproducing a contenttransmitted from said server; and transmitting client informationrelated to said client to said server every time the client informationchanges.
 338. A computer program product causing a client connectable toa server to perform the steps of requesting said server to transmitfirmware.
 339. The computer program product according to claim 338,further causing said client to perform the step of receiving a firmwarelist transmitted from said server, wherein said step of requestingselects firmware to be transmitted in said received firmware list. 340.The computer program product according to claim 338, wherein said stepof requesting requests said server to provide a specified amount offirmware.
 341. The computer program product according to claim 340,wherein said step of requesting transmits an obtaining start addressindicating the first address where firmware to be obtained from saidserver is stored and an obtaining data length indicating the length ofthe firmware to be obtained from said server.
 342. The computer programproduct according to claim 338, further causing said client to performthe step of requesting said server to provide a specified amount of afirmware list.
 343. The computer program product according to claim 342,wherein said step of requesting transmits a firmware list requestcommand including an obtaining start index indicating the first firmwareinformation to be obtained from said server and an obtaining numberindicating the number of pieces of firmware information to be obtainedfrom said server.
 344. A computer program product causing a clientconnectable to a plurality of servers to perform the steps of:connecting with any one of said plurality of servers; and determiningwhether connection with the server by said step of connecting ismaintained at prescribed intervals, said step of connectingreestablishing connection with said server when said step of determiningdetermines that the connection is closed.
 345. The computer programproduct according to claim 344, wherein said step of connectingestablishes connection with another server when the connection with saidserver cannot be reestablished.
 346. The computer program productaccording to claim 344, wherein said step of connecting transmits aclient status before the connection is closed to the connected server.347. A computer program product causing a monitoring client monitoring areproducing client reproducing a content transmitted from a server, andsaid monitoring client connectable to said server, to perform the stepsof: receiving the client information related to said reproducing clienttransmitted from said server; and displaying said received clientinformation.
 348. The computer program product according to claim 347,further causing said monitoring client to perform the step of changingthe display of said received client information when said clientinformation is changed.
 349. The computer program product according toclaim 347, wherein said client information includes the name of a dataformat of a content reproducible by said reproducing client, saidcomputer program product further causes said monitoring client toperform the step of displaying the name of said data format based onsaid received client information.
 350. The computer program productaccording to claim 349, further causing said monitoring client toperform the step of: obtaining a content list of a plurality of contentsfrom said server; and displaying a content reproducible by saidreproducing client among the contents included in said obtained contentlist and displaying a content that cannot be reproduced by saidreproducing client in a different manner from the reproducible contentor not displaying the irreproducible content.
 351. The computer programproduct according to claim 347, further causing said monitoring clientto perform the step of determining whether a client to be monitored issaid reproducing client.
 352. The computer program product according toclaim 347, further causing said monitoring client to perform the stepof: obtaining a monitoring handle necessary for monitoring saidreproducing client; and monitoring said reproducing client using saidobtained monitoring handle.
 353. A computer program product causing aserver connectable to a first client reproducing a content and a secondclient monitoring said first client, to perform the steps of: storing aplurality of contents in a storage device; transmitting a contentselected among said plurality of contents to said first client; andtransmitting client information related to said first client, to saidsecond client.
 354. The computer program product according to claim 353,wherein said step of transmitting client information transmits saidclient information to said second client through a push port for forcinga request to be transmitted to said second client.
 355. The computerprogram product according to claim 353, further causing said server toperform the step of returning a content list of said plurality ofcontents in response to the request from said second client.
 356. Thecomputer program product according to claim 355, wherein said clientinformation includes a list construction key necessary for producingsaid content list, and said step of returning produces said content listbased on the list construction key transmitted from said second client.357. A computer program product causing a monitoring client monitoring areproducing client reproducing a content transmitted from a server andconnectable to said server, to perform the steps of receiving clientinformation related to said reproducing client from said server;requesting said server to provide a content list of a plurality ofcontents, and receiving the content list returned from said server. 358.The computer program product according to claim 357, wherein said clientinformation includes a list construction key necessary for producingsaid content list, and said step of requesting transmits the listconstruction key included in said received client information to saidserver when the list construction key is changed.
 359. The computerprogram product according to claim 357, wherein said client informationreceiver receives said client information when said monitoring client isconnected to said server.
 360. The computer program product according toclaim 359, wherein said client information includes a list constructionkey necessary for producing said content list, said step of requestingtransmits the list construction key included in said received clientinformation to said server.
 361. A computer program product causing aserver connectable to a first client reproducing a content and a secondclient monitoring said first client using an obtained monitoring handlenecessary for monitoring said first client, to perform the steps of:storing a plurality of contents in a storage device; transmitting acontent selected among said plurality of contents to said first client;determining whether said second client has said monitoring handle; andtransmitting client information related to said first client, to saidsecond client when said second client has said monitoring handle basedon the result of said determination.
 362. A computer program productcausing a control client controlling a reproducing client reproducing acontent transmitted from a server and connectable to said server, toperform the step of requesting said server to control said reproducingclient.
 363. The computer program product according to claim 362,wherein said step of requesting transmits information for specifyingsaid reproducing client and information for specifying said content tosaid server.
 364. The computer program product according to claim 314,wherein said step of controlling controls said first client through apush port for forcing a request to be transmitted to said first client.365. The computer program product according to claim 362, furthercausing said control client to perform the steps of: determining whethera client to be controlled is said reproducing client, and controllingsaid reproducing client when said reproducing client is to be controlledbased on the result of said determination
 366. The computer programproduct according to claim 362, further causing said control client toperform the steps of: determining whether the data format of saidcontent matches the data format of the content that can be reproduced bysaid reproducing client; and instructing said reproducing client toreproduce said content when said data formats match.
 367. The computerprogram product according to claim 362, further causing said controlclient to perform the steps of: obtaining a control handle necessary forcontrolling said reproducing client; and controlling said reproducingclient using said obtained control handle.
 368. A computer programproduct causing a server connectable to a first client reproducing acontent and a second client controlling said first client, to performthe steps of storing a plurality of contents in a storage device;transmitting a content selected among said plurality of contents to saidfirst client; determining whether or not said second client has acontrol handle necessary for controlling said first client when saidsecond client requests said server to issue a server request; andtransmitting said server request to said first client when said secondclient has said control handle based on the result of saiddetermination.
 369. The computer program product according to claim 362,further causing said control client to perform the steps of: receiving acompletion status transmitted from said reproducing client through saidserver; and instructing said reproducing client to reproduce the contentnext to the content that has been reproduced to the end in response tosaid received completion status.
 370. A computer program product causingan AV equipment being controlled by a first client connected to a serverand connectable to a second client connected to said server, to performthe steps of: receiving a control command transmitted from said firstclient through said server and said second client; and controlling acontrollable element in said AV equipment in response to said receivedcontrol command.
 371. A computer program product causing an AV equipmentconnectable to a relay client connected to a server, to perform thesteps of receiving a content selected among a plurality of contentsstored in said server from said server through said relay client; andreproducing said received content.
 372. The computer program productaccording to claim 371, further causing said AV equipment to perform thesteps of: transmitting information related to said AV equipment to amonitoring client monitoring said AV equipment through said relay clientand said server.
 373. A computer program product causing a serverconnectable to a first client reproducing a content and a plurality ofsecond clients instructing said first client to reproduce the content,to perform the steps of: storing a plurality of contents in a contentstorage device; transmitting a content selected among said plurality ofcontents to said first client; selecting one of said plurality of secondclients and transmitting a completion status indicating completion ofreproducing the content to the selected second client when receiving thecompletion status from said first client.
 374. The computer programproduct according to claim 373, further causing said server to performthe step of managing the priorities of the second clients that cancontrol said first client; and said step of selecting selects a secondclient with the highest priority as the second client to receive saidtransmitted completion status.
 375. The computer program productaccording to claim 374, wherein said step of selecting transmits a stopstatus to the second client other than the second client with thehighest priority.
 376. The computer program product according to claim373, further causing said server to perform the steps of: storing theidentification information of said second client that has instructedreproduction in a memory, and said step of selecting transmitter selectssaid second client that has instructed reproduction as the second clientto receive said completion status based on said stored identificationinformation of the second client.
 377. The computer program productaccording to claim 376, wherein said step of selecting transmits a stopstatus to the second client other than said selected second client. 378.A computer program product causing a control client controlling areproducing client reproducing a content transmitted from a server andconnectable to said server, to perform the steps of: obtaining a controlhandle necessary for controlling said reproducing client; specifying acontent among a plurality of contents stored in said server afterobtaining said control handle and instructing said reproducing client toreproduce the specified content; and specifying a content next to thecontent that has been reproduced to its end by said reproducing clientin response to a completion status indicating completion of reproducingthe content received from said reproducing client whose control handleis obtained by said control client and instructing said reproducingclient to reproduce the specified content.
 379. The computer programproduct according to claim 378, wherein said step of obtaining, uponobtaining said control handle, prohibits the other control client fromobtaining said control handle.
 380. The computer program productaccording to claim 296, further causing said control client to performthe step of: canceling the prohibition of obtaining said control handlein response to a stop status indicating stop of reproducing the contentmidway, said stop status received from the reproducing client whosecontrol handle is obtained by said control client.
 381. A computerprogram product causing a server connectable to a first clientreproducing a content and a second client instructing said first clientto reproduce the content, to perform the steps of. storing a pluralityof contents in a content storage device; transmitting a content selectedamong said plurality of contents to said first client; and specifying acontent next to the content that has been reproduced to its end by saidfirst client and instructing said first client to reproduce thespecified content in response to a completion status indicatingcompletion of reproducing the content, said completion status receivedfrom said first client,.
 382. The computer program product according toclaim 381, further causing said server to perform the steps of: storinga list construction key necessary for producing a content list ofcontents to be reproduced by said first client in a memory; andproducing said content list based on said list construction key; andsaid step of specifying instructing said first client to reproduce saidcontent according to said content list.
 383. A computer program productcausing a reproducing client being controlled by a control clientconnected to a server and connectable to said server, to perform thesteps of reproducing a content specified among a plurality of contentsstored in said server in response to an instruction from said controlclient; receiving a list construction key necessary for producing acontent list from said control client and transmitting the listconstruction key to said server; receiving the content list producedbased on said transmitted list construction key from said server; andreproducing a content next to the content that has been reproduced toits end according to said received content list.
 384. A computer programproduct causing a reproducing client being controlled by a controlclient connected to a server and connectable to said server, to performthe steps of: reproducing a content transmitted from said server; andtransmitting a completion status to said server when finishedreproducing a content as instructed by said control client andtransmitting a stop status different from said completion status to saidserver when finished reproducing a content selected by said reproducingclient or stopped reproducing the content midway in response to theoperation of the user.
 385. The computer program product according toclaim 353, further causing said server to perform the steps of receivingclient information related to said first client from said first client;and said step of transmitting client information transmitting saidreceived client information to said second client.